> -----Original Message----- > From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED]] > Sent: Thursday, 29 November 2001 6:29 pm > To: [EMAIL PROTECTED] > Subject: Re: data goes in, data goes out >
<snip/> > The URI schemes I find useful for Cocoon are: > > 1) file: -> obviously > 2) dbxml: -> obvious again > 3) http: -> reading is done thru GET, writing thru PUT or POST > 4) webdav: -> [should this be different from HTTP?] > 5) cvs: -> would allow Cocoon to generate the documentation directly > out of CVS. A plus when you don't have much local storage capacity (say > on diskless embedded system, but maybe this is FS) Na - I'd like to query a cvs server via cocoon. I've just never gotten a net connection with sufficient bandwidth to inspire me to write the code. > 6) ftp: -> nobody uses FTP nowadays, but legacy systems do. > 7) imap: -> would be killer for cocoon-based webmail application (I > know Gianugo was thinking about implementing this) but probably a direct > javamail interface would be much more useful. > 8) smtp: -> would allow us to serialize a pipeline on email. Might be > useful or might be FS, see above. > > what I don't really find useful are: > > 1) sql -> how do you map a table with a path? sql -> path is easy... sql:/databasename/table/field queries - now that's another matter :) J. <snip/> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
