sorry, i have not made myself clear and the many typos won't have helped either. I need both ends of the connection to be able to read and write data. I will outline the process here:
1) user runs client using config file containing username/passwd/domainname 2) client connects to server and awaits ready code 3) server sees client and checks sends a ready code 4) client sends config file info to server 5) server calls sub in a module to validate username/password/domain 6) if all ok then send "ok" to client else send "not ok" 7) client sees "ok" and sends ip update request 8) server updates database The server is running in inittab so no output is seen, but the client will print error codes and interpretations to STDOUT anyone willing to write me some quick examples. PS, the server needs to be forking (multithreaded) On Mon, Sep 23, 2002 at 10:24:31 -0400, Bob Showalter wrote: > > -----Original Message----- > > From: Mat Harris [mailto:[EMAIL PROTECTED]] > > Sent: Monday, September 23, 2002 4:19 AM > > To: [EMAIL PROTECTED] > > Subject: client-server with socket > > > > > > i have got the multithreaded server example from perldoc but > > i need a client > > that will connect, and upon recieving a certain work from the > > server, send > > some authentication details and the current ip address of the client. > > > > this is for a dynamic dns solution. I need to have the client send and > > recieve info to and from the server, but there don't seem to > > be any examples > > of this 2-way conversation. > > I'm not sure I understand the question, but DNS client functionality is > typically a part of your standard OS libraries. (see 'man resolver'). > Net::DNS provides a Perl interface to this. You shouldn't try to write your > own resolver, IMO. -- Mat Harris OpenGPG Public Key ID: C37D57D9 [EMAIL PROTECTED] matthewh.genestate.com
msg30982/pgp00000.pgp
Description: PGP signature
