To us:
Option 1 makes more sense if you don't have a server side objects, as
just all clients will be Windows or Linux based.
However, we have chosen option 2, as we want to migrate to server side
objects that we wish to host on a number of different operating systems.
We could not find a cost effective way of connecting Delphi clients to
Java server side objects. With the advent of SOAP that might be about to
change... I would be interested to hear anyone's thoughts and
experiences about this...
Option 3 is loved by our management, but to us developers it feels
rather like chopping our arms off...
Martin
> -----Original Message-----
> From: Neven MacEwan [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, 22 November 2000 11:25 a.m.
> To: Multiple recipients of list Delphi
> Subject: [DUG]: Offtopic (Sort of)
>
>
> Hi All
>
> Since the list police seem to be all asleep and lively
> discussion is the
> order of the day then
> give the spec of a clients requirement for a database (sql) app (and
> ignoring middleware requirements)
> would you on the client side use
>
> 1/ Delphi/Kylix (and limit your target clients to Windows/Linux)
> 2/ Write it a Java GUI (and therefore have every graphical platform)
> 3/ Use a Browser (as 2)
>
>
> Regards Neven
> N.K. MacEwan B.E. E&E
> Ph 649 574 0027
> Fax 649 570 2706
>
> "A truth denied the light of action will wither to a promise,
> propaganda and
> then a lie"
>
> --------------------------------------------------------------
> -------------
> New Zealand Delphi Users group - Delphi List -
> [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
> To UnSub, send email to: [EMAIL PROTECTED]
> with body of "unsubscribe delphi"
>
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
