One of the most exciting aspects of P2P is its use as an enabler of specific communities. I am interested in creating distinct XML types for documents that support workgroups, such as designs, presentations, pricing, etc., described by metadata specific to those domains.

Has anyone extended the XML description set and added to the overall messaging set to support a secure, custom application? I am working on a version of Limewire for knowledge sharing in which the metadata works both ways -- a query is sent out based on a subset of an object's ontology, and the entire set is returned and displayed in the result set. As a primitive example of this, look at the way KaZaa includes a keyword set and comments that are displayed in flyovers for each located file. I want to create a version of Limewire the is extensible based upon the XML descriptors only.

I have just begun analyzing the 2.8.5 source, so much of this may already be available. If so, is there a description of the QueryReply mechanisms and code that would point to how this would best be extended?

Thanks,
John Martin

It would be trivial to create your own xml schemas for "documents" for example. All you would have to do is to create an .xsd file like the ones for audio and video searches and put it into the xml.war (a renamed .jar file).

Making LimeWire secure is a llittle more difficult, I know the LimeWire developers have created an authentication method, for connecting to LimeWire but I don't never looked at it in detail.

Better ask them developers yourself at dev@core.limewire.org.

__________________
Morgens ess ich Cornflakes und abends ess ich Brot
Und wenn ich lang genug gelebt hab, dann sterb ich und bin tot

--Fischmob

Thanks. I have looked at the XML code and modules like TableLine.Java, and have noticed that there is a lot of schema-specific code. There are hard-coded references to "audio.vxd" and "video.vxd"

I was hoping -- and it may work this way -- that by adding schemas to the xml.war file, the GUI and TableLine would be smart enough to add the schema to the file type selection and to parse the schema to create a metadata input dialog.

Thanks,
John Martin

... Yeah, that'd be nice.