Cortlandt wrote:

> Mark,
>
> There is a problem with your question as you posed it because it is a
> *very* broad question.   Answers can vary widely depending upon
> factors such as:
>
> 1.  Do you wish to display a report or create a web version of a data
> entry screen?
> 2.  Do you have a requirement  to use the code from your current app
> or can you go directly to the data base?
> 3.  Do you anticipate developing more of these in the future?
> (Determines how much infrastructure it makes sense to buy/build and
> implement)
>

The questions he poses are significant. They reflect the "multi-dimensional"
need to use MPE data and logic in unanticipated ways. What starts out as a
need to show Image data within a web browser, often ignites the demand to
make that data available in all sorts of "client" applications. What often
begins as a need to retrieve and display comes full circle with new requests
to remotely update and transform. When the encapsulation of an application
is done by providing a "services" layer, a layer which protects, and
decouples, then all sorts of future integration scenarios can be supported.

When I read Cortland's questions, I think the best answers are the ones
which provide for future flexibility. 1) Yes, 2) Yes, and 3) Yes - that is
if one is planning to develop a resilient and responsive architecture.

Regards,

Jonathan van den Berg
Premier Software Technologies
fon: 408-257-8757
fax: 408-253-1184
www: http://www.premiersoft.com