i'll answer my own questions...
> ok, but how do you read the info or request it?
> suppose you know the ip and port to use only?
according to what i saw in the ftp client made with MC (listed in the
www.xworlds.com contributions...
What you have to do is to open the socket
The port is for example 80 for a web server, 21 for ftp, etc (see the RFCs
(ez to find at yahoo) for most common server formats). Other programs like
game servers or particular programs (CUCME, Roger Wilco, Hotline,
MSNMessenger, etc...) depend on the program. Finding those protocols and
datagrams is not easy. You'll have to look for source code or sniff the
packets... Source code is usually easier to find.
(Debugging note: a firewall program can block your packets so make sure that
they pass first. You can ping the server for example but some firewalls will
block either the address (websense.com) or the ports or any combination of.
Ask the net administrator at your work place. Just remember that this would
imply that the program you would try to emulate would not work either since
they would also be blocked.)
Once you've opened the socket using the right "ip:port" url, you'll have to
send it some datagrams or a message.
For http, it's a message and for a quake server it's a datagram.
If you dont send anything, the connection will simple open and close
(right?).
So you write the socket a query
in http, it can be "GET,OPTIONS,etc... (thanks to Spade.org)
in quake, you have to send it datagrams (thanks to Qstats and source code at
http://www.activesw.com/people/steve and Luc the fragmaster at
http//3d.win.be/
if you dont do that, you wont get anything...
i still havent got anything from any quake servers yet but soon i hope!
The FTP client is a great example on how to use the sockets
and you can read it's source in the stack script.
It's a good explanation of how an ftp server works!
im writting a socketsbrowser, it should be ready for xmas!
Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
