R
Richard Anderson
I *knew* there was a Perl question lurking in there somewhere. We just
had to find it.
To start learning about network programming in Perl, have a look at
"perldoc perlipc", especially the section "Sockets: Client/Server
Communication". That's low-level stuff though. If you're using a
well-known protocol - heck, even if you're using an obscure protocol,
have a look around CPAN to see if there's a module that implements it.
Once your app is listening for and accepting connections, it can also
send responses. If you want to be sneaky, set up your app as a "man in
the middle". When it gets an incoming connection, establish a
connection with the real app too.
You can then write your app to handle the CPU ID request however you
want, but forward other requests to the main app and return its
responses back to the server, either as-is or modified.
There's no way for me to know that. That's what the packet scanner is
for, so you can examine the traffic between the client and server.
You'll need to decide how to proceed based on what you see there.
sherm--
Thanks alot Sherm! You helpes me clarify steps.
Exmm is there a way that you can also contribute to the perl prog i have
so far by adding network programming support?