I have a couple of these sort of apps (commerical so I can't give you source
- sorry)
The old style approach, which is still used, is to use a serial comms or RAS
component on both client & server end & handle the details of the client
dialling up the host (ie send ATDT nnnnnnn to the serial port) & exchange
data via a protocol like X-Modem or Z-Modem. You should be able to find
source for BBS type systems that does this. Another approach like this would
be to use X-25 but I wouldn't bother as....
The best approach, IMHO is to use something like the ICS component suite &
drop in the FTP server & FTP client components. We got a full blown
transaction processing system going in a few days (following a couple of
weeks planning & documentation <g>) using these components. Using standard
components means that you do not have to worry about the details of the user
dialing - all they have to do is get set up with an ISP (which is not your
problem).
-----Original Message-----
From: Matthew Comb [mailto:[EMAIL PROTECTED]]
Sent: Friday, 18 February 2000 10:23
To: Multiple recipients of list delphi
Subject: [DUG]: Dialup.
Hi Guys,
if you had to write an app to allow someone dialling in to connect then to
copy files back and forth where would you start?
I assume I would have to write an app for both ends. The receiver would be
95/98/NT but the dialler would be NT based.
Any thoughts?
Cheers,
Matt.
The Rules Have Changed...Get Paid to Surf the Web!
http://www.alladvantage.com/go.asp?refid=ggz487
<http://www.alladvantage.com/go.asp?refid=ggz487>
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
