Re: Object->XML serialization [was Re: AxKit Users?]
On Wed, Jan 31, 2001 at 03:03:56AM +0100, Robin Berjon wrote: > > > >Alzabo (which is somewhat the opposite of Tangram) is designed with > >mod_perl in mind. XML serialization will be coming real soon now (as soon > >as Barrie Slaymaker finishes work on DBML). Cool. More pressure ;-). Anyway, we're just about through the "beta gauntlet" and I'll be able to get DBML packaged. Anyone that wants a tarball, just ask. - Barrie
Re: Object->XML serialization [was Re: AxKit Users?]
On Wed, 31 Jan 2001, Robin Berjon wrote: > >Alzabo (which is somewhat the opposite of Tangram) is designed with > >mod_perl in mind. XML serialization will be coming real soon now (as soon > >as Barrie Slaymaker finishes work on DBML). > > Ah, the eternal hesitation... Alzagram any time soon ? Well, they do largely the opposite thing. Tangram maps objects onto databases and Alzabo maps databases onto objects. Admittedly, Alzabo has some features that let you do some (thought not close to all) of what Tangram does but they're really different things. -dave /*== www.urth.org We await the New Sun ==*/
Re: Object->XML serialization [was Re: AxKit Users?]
At 19:58 30/01/2001 -0600, Dave Rolsky wrote: >On Tue, 30 Jan 2001 [EMAIL PROTECTED] wrote: >> It would be nice to see "xml marshalling" (as they call it) integrated >> into an existing Perl object-relational framework like Tangram. OTOH, >> Tangram isn't very well optimized for mod_perl work in general--currently >> the object cache must be completely flushed after each request, etc. > >Alzabo (which is somewhat the opposite of Tangram) is designed with >mod_perl in mind. XML serialization will be coming real soon now (as soon >as Barrie Slaymaker finishes work on DBML). Ah, the eternal hesitation... Alzagram any time soon ? -- robin b. Smoking is one of the leading causes of statistics.
Re: Object->XML serialization [was Re: AxKit Users?]
On Tue, 30 Jan 2001 [EMAIL PROTECTED] wrote: > It would be nice to see "xml marshalling" (as they call it) integrated > into an existing Perl object-relational framework like Tangram. OTOH, > Tangram isn't very well optimized for mod_perl work in general--currently > the object cache must be completely flushed after each request, etc. Alzabo (which is somewhat the opposite of Tangram) is designed with mod_perl in mind. XML serialization will be coming real soon now (as soon as Barrie Slaymaker finishes work on DBML). -dave /*== www.urth.org We await the New Sun ==*/
(Correction) Re: Object->XML serialization [was Re: AxKit Users?]
On Tue, 30 Jan 2001 [EMAIL PROTECTED] wrote: > Castor (for Java, from www.exolab.com), uses an actual XML Schema for > this. The advantage is that you can leverage off the fairly rich existing > set of defined datatypes. Sorry, it's www.exolab.org, don't you hate that? --Chris
Re: Object->XML serialization [was Re: AxKit Users?]
At 15:29 30/01/2001 -0800, [EMAIL PROTECTED] wrote: >It would be nice to see "xml marshalling" (as they call it) integrated >into an existing Perl object-relational framework like Tangram. OTOH, >Tangram isn't very well optimized for mod_perl work in general--currently >the object cache must be completely flushed after each request, etc. That is only half true. When running 5.6 (ie when you have weakrefs) Tangram takes advantage of it to avoid circular refs. Depending on the number of distinct objects that you load it could still be a good idea to $storage->unload in your cleanup handler, but that wouldn't necessarily be the general case. And anyway, when I mention XML I'm talking about Tangram 2. I haven't tested it yet, but I'll soon have a chance to. I'll probably report to the modperl list when this happens. A number of things have changed there. I've also found Jean-Louis Leroy to be very supportive, he even came to meet me to ask me questions about what modperl users of Tangram needed (if you have a list of issues, pass it on to me, I'll summarize and discuss it with him). I'd expect Tangram to move forward quite fast in the times to come. >I think an open-source mod_perl-oriented O/R system with XML support would >be extremely useful. I would be interesting in hearing opinions on whether >extending Tangram and its ilk is viable. Either way, I will probably look >into working on this in the near future, let me know if you're interested. Extending Tangram is viable. It will become even more so shortly. I'm definitely interested if you decide to work on this. -- robin b. Smoking is one of the leading causes of statistics.
Object->XML serialization [was Re: AxKit Users?]
Castor (for Java, from www.exolab.com), uses an actual XML Schema for this. The advantage is that you can leverage off the fairly rich existing set of defined datatypes. It would be nice to see "xml marshalling" (as they call it) integrated into an existing Perl object-relational framework like Tangram. OTOH, Tangram isn't very well optimized for mod_perl work in general--currently the object cache must be completely flushed after each request, etc. I think an open-source mod_perl-oriented O/R system with XML support would be extremely useful. I would be interesting in hearing opinions on whether extending Tangram and its ilk is viable. Either way, I will probably look into working on this in the near future, let me know if you're interested. --Chris On Tue, 30 Jan 2001, Matt Sergeant wrote: > On Tue, 30 Jan 2001, Robin Berjon wrote: > > > >Well OK then, lets look at a way to dump current objects to XML, or > > >interface to what you've got. I think that could be useful to a lot of > > >people (myself included). > > > > Yes that would be indeed very interesting. It can't be totally automagic > > *and* be useful in the context that I (and I guess others) need, which is > > to dump an object into a vocabulary that makes sense wrt the app. The way I > > see it is that it's more or less schemata the other way round: given an > > infoset (more or less) and stuff to fill it with, and produce a document. > > Maybe a small language defining that would be both possible and good. > > In fact it could be an XML vocabulary, similar to TREX, something like: > > > > > > > > > > > > > > >
