p2p, the module way

[jesta]

hi folks.

now since im new to this forum and to the deeper knowledge of p2p networking (not that i haven't been using software) you can simply correct me on any mistakes i make.

now this is why i post: i did some thinking on this whole concept right now and did some reading and did some wondering: is there something like a p2p client that does not only some services like file sharing, messaging, chatting, etc. but that is actually open to ANY kind of service? i mean like a barebone p2p software that does nothing more than establish the connection to other peers so that 3rd party programs can then use this connection for their service?

because this would in my opinion be a step towards integrating p2p into ANY application that needs communication with distant computers. imagine having a small app that runs in the background in your startup and does nothing more than finding a couple of other peers when launched. then when you want for example to get a file you launch another prog that utilizes the established connection and searches for it. i dont mean that the connecting prog and the sharing prog are inseparable. there could be a whole variety of different progs that all use their own interface and specialise in their own filetypes, written by a variety of different developers.
now if you want to send instant messages you launch your icqp2p or whatever you prefer and it searches for your buddy "gizmo123" by sending a search request using the connection app.
there is even the possibility to have a hybrid p2p network IN the pure p2p network by running node programs on the connection program if any program or task requires it.

there is one problem which remains for me: how does a computerin a pure p2p network find the first peer? just by trying a specified port on any given adress until there is a response? that has to take ages on a very young network with a small number of peers... and how many connections should be maintained by the program or is it smarter to sort of collect peers, store them, say a thousand adresses, refresh them from time to time to sort out the ones not responding any more and fetch new ones and then send the search requests to all the stored adresses? explain please

now if there is a program or concept like the one i descibed please just point me to it and this thread is finished and if there isn't, tell me wether this is possible at all.

jesta

[DigitalJunkie]

There is no such p2p core engine that everybody would use. It's more complex, each p2p network need "protocols" on client/server to communicate to work together, so it can serach for peers, file(s), type of encryption or hash system if wanted, etc.! Different developers have different ideas what their p2p is going to be like from start to finish. Be glad they are different, otherwise I wouldn't use it. "There are safety in numbers!"

[jesta]

i think i did not make my point clear there: the core engine wont have a protocol for transfering files. it will just serve the p2p programs by establishing the connection. the program then using this connection would have it's own protocol.
Looking at it this way its a little bit like the tcp/ip protocol i'd guess. it serves to establish the connecdtion, in this case to the net, and the programs using it have their verry own protocol...

jesta

[DigitalJunkie]

Connection needs different protocols, such as http, tcp, udp, etc. Not all p2p uses all. Some any just use udp, others may use combination of tcp/udp. Like I said, different developers like different ideas.