> With this library shouldn't be that hard to build a writable source... I > just wonder how the URI would turn out to be... mapping the CVS resource > resolution space (with tags, branches and versions) to a URI space looks > pretty scary to me... (look at the mess that WebDAV DeltaV had to go > thru!)
<ignornace mode="on"> Wouldn't that depend on whether the request was being handled via GET or POST? This sounds like the kind of thing that the W3 TAG has been getting into with respect to SOAP. If all of the extra goop can be transmitted "out of band" from the URI, then the problem would go away. So can a source access out-of-band information? Put the details in an XML document (like a SOAP request) and Bob might be your uncle. </ignorance> Jason Foster --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
