On 30/12/02 23:00, "Stefano Mazzocchi" <[EMAIL PROTECTED]> wrote: > > Even Pier told me once that he would be interested in something like > this since he is, in fact, already using XML->text serialization (but > not thru Cocoon or James) to run the notification services his company runs.
Correct... For my employer, basically every email we send is rendered from an XML document (or something that at the end, is consumed from SAX events). Our model might not fit entirely in Cocoon, as we tie some of our processing to DartMail from DoubleClick, but some of the components can be indeed reused, like the text/plain writer (a renderer for a pseudo-HTML-like format into plain text) and our "mime writer" (basically dealing with an XML-based representation of a multipart MIME document, writing down chunks and correctly encoding the whole kit'n'kaboodle, including i18n)... My management is saying that they don't really mind if I "give those bits away for free", so, from next year the classes will all be available in the open... The only concern VNU still has is the "control" on the interfaces ATM, given that we use those two tools every day in production, and my management is scared by a possible "denaturation" from our original "KISS" (keep it stupid and simple) idea. Currently, both of them are simple SAX consumers (implementing DocumentHandler), and we are planning to start distributing them with a BSD license from http://www.vnunet.org/... Note, the site is not yet up, if you want to get a peek at the code, just ask, but I need to "legally" prepare it before anyone can use them... Pier -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
