Question For Experts

[insanehadi]

am trying to create a client that connects to a p2p network called ares .. that includes a chat .. my question is how can i use the program's protocol to create this client i want ... ? I have the Protocols ... please Help !

[Jim Davis]

Hello and welcome to the forums.
You have to ask your questions with even more details about what do you want to do, and what help you are looking for. You may want to write about the protocol you got, that may be helpful to others, to find the best solution to you.

Mostly, p2p networks are using multiple connections, that is you can do, by placing a Winsock control on your form, and set its index property to 1. Now you can instantiate multiple copies of this control, so you can build up connections to multiple clients and/or servers.

[insanehadi]

http://www.freewebs.com/aresprotocol/

these are the protocols for ares ... ares was programmed with the Language delphi btw

[insanehadi]

Thank you so much jim ,,, if u are wondering these are the ares protocols .. http://www.freewebs.com/aresprotocol/ ... and ares was programmed usgin delphi

[Jim Davis]

As it just looks like, this is a protocol that uses server to communicate with. This is not called p2p. p2p is a kind of connection structure, there clients are connecting to each other and building up a network (that is called a p2p network). Torrent is a good for example for what is p2p.

Msg_CCache_Here_Channel:

Command ID: 0x48 [72]
Sender: Server
Data Format: [4 Bytes -
External IP Address] [2 Bytes - Port] [2 Bytes - User Count] [Null Terminated - Channel Name]
[Null Terminated - Topic] [4 Bytes - Internal IP]
Description:
Channel, This data is zipped when it is sent. Internal IP Address is only
sent if it is different than external ip.

This protocol also using ziplib to compressing the content. This is a CPU hog, however using less bandwith than MSN or other chat clients.

Edit: by checking more depth, it seems like it is a p2p, because using super nodes to connecting to. However, this protocol documentation is not so detailed, it just talk about the command codes. There should be informations about the connection structure (sequence), what command will follow which one etc...