Gidday Tracey, > just wanting some input really... > > I am looking at developing an application which will need to access one database >from two different locations, via the internet. > of course i could just wizz up another cgi app... but i would like to try something >different as this is the only area i have done any serious development in delphi. > > What would be your choice?
Here's a couple of options: 1. If it's intended to be GUI on both systems, you could use straight TCP/IP for a back-end like Interbase. Internet transfer speeds and latency may or may not be a problem, depending on the quality of your connections and the nature/volume of the data you are passing. The advantage is obviously that you're really just creating another C/S app from your perspective. 2. Where a browser interface is desirable -- usually when we want connection pooling for variable load, etc., we generally use WebHub for Delphi (http://www.webhub.com) to create a state-ful server app which ties directly to the database, and run the Web clients against that. We've also run GUIs against that kind of back-end where required, using HTTP requests/posts to transfer the information. All more work than (1), but very flexible/scalable, and far better at coping with real-Internet conditions. . cheers, peter =========================================== Peter Hyde, SPIS Ltd, Christchurch, New Zealand * TCompress/TCompLHA component sets for Delphi/Kylix/C++ * TurboNote+: http://TurboPress.com/tbnote.htm -- top-rated onscreen sticky notes * Web automation for online periodicals: http://TurboPress.com Find all the above and MORE at http://spis.co.nz --------------------------------------------------------------------------- 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" Web Archive at: http://www.mail-archive.com/delphi%40delphi.org.nz/
