Drew Taylor wrote: > If you go this route, you might want to take a look at XML::Comma, > which stores all its data in XML files and then turns them into objects > as needed.
I was just looking at XML::Comma earlier today. (It seems to get mentioned in job postings with some regularity.) It's described as being an "information management platform," but based on reading the documentation (http://xml-comma.org/guide-filter.html) it seemed to be primarily an XML storage system. Given how it is described and the context in which it is used, I was expecting to see high level content management functionality. For example, while there was lots of discussion on how you read and write data stored in the XML documents, I didn't see anything addressing how you transform them into HTML. There was mention of HTML::Mason handlers, but I didn't see any specifics. (I'm not particularly fond of the HTML::Mason model.) Based on that I'd speculate that it's more of a cobbled together solution (it uses a combination of XML files in the file system and indexes stored in an RDBMS), compared to the native XML databases, if XML storage is what you're looking for. On the other hand, XML::Comma may offer superior Perl integration than the other solutions. -Tom _______________________________________________ Boston-pm mailing list Boston-pm@mail.pm.org http://mail.pm.org/mailman/listinfo/boston-pm
