cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Morrison" <john.r.morri...@ntlworld.com>
Subject RE: data goes in, data goes out
Date Thu, 29 Nov 2001 19:06:58 GMT
> -----Original Message-----
> From: Stefano Mazzocchi [mailto:stefano@apache.org]
> Sent: Thursday, 29 November 2001 6:29 pm
> To: cocoon-dev@xml.apache.org
> 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: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message