We have a generic mechanism for sending messages from a node to its direct peer. At the moment this is only used for sending fproxy text messages, but it can be used for much much more.
It might be useful to: - Change the string we now send to a bytearray. This is more generally useful. - Expose the node to node messaging system via FCP. It already has an integer for node to node messages; we can either maintain a registry of service numbers, (32 bits should be adequate!) or expand it to a service name string. - Provide for discovery of such services by telling sufficiently trusted nodes which services are registered. When a sufficiently trusted node connects, we would send a series of FNPServiceRegistered messages, each of which would contain an ID for node to node messaging, and a short block of data indicating its current status. When a new service is registered likewise we would announce it to our trusted peers with the same message, and when one is removed we would send an FNPServiceUnregistered message. - Provide an easy means to transfer bulk data, as well as short messages, between services on one node and on its peer. Possible applications: - Instant text messaging via Fproxy. :) - Instant messaging via more interesting clients. Either something custom for Freenet, or a gateway to something widely used e.g. Jabber. - Bookmark sharing. - Sharing of file indexes (could be supported by Thaw). (Difficult without bulk data transfer as indexes may be large). - Sharing of local files. All of these things IMHO would provide an incentive for people to add darknet connections. -- Matthew J Toseland - toad at amphibian.dyndns.org Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20060630/81e6959b/attachment.pgp>
