Dennis,
Thanks for the thoughtfulness of your reply.
>Why do you say the web is out? With our web application, you can be using
it one minute, the connection can drop (due to the uncertain nature of
internet connections), and when you get the connection again, just continue
working. No big deal - as long as you design your comms protocol
properly.<
We are likely to be working offline 99% of the time, connecting only to
send/retrieve data. There is at least one alternative comms backbone we
will need to use too, but whether we work with two completely different
programs, one 'does everything' program, or two programs with a reasonable
level of commonality is TBD.
>The way this works is, the client makes a
connection to the server, requests for a page (data can be sent on the page
request), gets a page (data is retrieved on the reply) and closes the
connection.<
I agree we need something connectionless for scalability. An odd feature of
this system as it stands is that the client doesn't need to do any browsing
of databases on the server, just pick up whole (small) databases, and the
uploads would be best as text files too. In the future there may be a large
database to browse, but not yet. So, an FTP approach would work ok, but
there are too many security issues with that (other than the normal holes
there are privilege problems). I think a middle-ware solution will probably
be our best bet.
Thanks for your help,
Terry
---------------------------------------------------------------------------
New Zealand Delphi Users group - Offtopic List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
