Another idea (roughly):
1. Use MS SQL / MSDE (natural for ADO, see next point)
2. Use ADO (can easily share common _Connection object between many COM
objects, etc)
3. Create entire application as a series of COM objects with Delphi
(Business objects, Utility objects, DBLayer, etc - all the Non-GUI stuff)
4. Create all standard Browsers, Pickers, Editors as ActiveX controls with
Delphi
5. Create your non-web based client as a thin executable (in Delphi) using
all the ActiveX controls and COM objects in 3 and 4 above and only adding
the required plumbing.
6. Create your web-based clients using ASP to glue together all the required
COM objects created in 4 above. If ASP becomes too clunky you have the
option of using ISAPI dlls (using Delphi) or even Windows Script components,
etc
7. Think carefully about stateful vs stateless objects, you may want to
MTS-enable or ASP-enable objects in 4 above...
One of the fundemental ideas here is to use same objects between the
standard WinGUI and Web-based clients. If you are only ever going to have 1
single WinGUI, you may want to skip creating ActiveX controls as mentioned
in 4 above - doing it that way however will provide you with reusable GUI
components (nice if you need more than one GUI configuration). You could aso
use D5 Frames I guess...
Just another angle ...
Xander van der Merwe
----- Original Message -----
From: Juan Manuel Gomez Ramos <[EMAIL PROTECTED]>
To: Multiple recipients of list delphi <[EMAIL PROTECTED]>
Sent: Friday, February 04, 2000 7:13 AM
Subject: [DUG]: DB Server choice
> Hi there:
>
> I'm designing a client/server DB app for a travel agency. The server
> will be in the main house, and the clients all around the country, one on
> every sale point.
> There will be a web based client, programmed by someone else who defends
> the idea of using MS-SQL as the server app. I like (love) Delphi and would
> like to use Interbase as the server. The thing is that I need arguments to
> defend such idea 'cause this will be my first client/server project and
> I've never seen any documentation about Interbase before. Does it have the
> posibility to have the web based client programmed in something else than
> Delphi? If this is the case, I wouldn't worry any more; it would be just a
> matter of programming it and inform the other programer about the stored
> procedures to use to access the DB server. What softwares (compilers)
> could he use?
> Another question is: What protocols does Interbase use/have? Which is
> the fastest one. I was thinking on hosting the web based client app
> outside the country, to provide users a faster connection to it but, if
> it must access a DB server located here in Cuba, then thats a slow way to
> connect.
> Anything you may say about it would be a well apreciated lesson to me.
> You might need more info; just ask. Thanks in advance.
>
> Juan Manuel Gomez Ramos
> Computer Science student at Havana University
> Paraglider pilot and RadioHam (CM9BPG)
>
> email:<[EMAIL PROTECTED]>
> <[EMAIL PROTECTED]>
> eFax:(707) 313-0329
> http://cronos.freeservers.com
>
> Hope is faith holding out its hand in the dark.
>
>
>
>
>
>
>
>
> --------------------------------------------------------------------------
-
> New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
>
>
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
