OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: [xml-dev] xml xsl web architecture

[ Lists Home | Date Index | Thread Index ]

On 2/27/06, Anthony Ettinger <aettinger@sdsualumni.org> wrote:
> > >
> > > L10N support, large-scale public web sites, accessible on multiple
> > > platforms.
> >
> > Targetting 10,000's or millions of users?  Lots of content (CMS)?
> > Forms? Ecommerce (back end databases)?  Any target deployment
> > platforms biases (Windows, Linux)?
> Lots of content, 1000+ pages, millions of users,
> linux+apache+php5+mysql/postgresql
> I don't see how this makes a difference in the xml architecture though

It may or may not make any difference, it does help me get a feel for
what types of solutions and architectures you might be comfortable
with.  Bear with me and I'll digress a bit on how/why...

A shop such as yours might be a lot more comfortable with a solution
such as JBoss or Apache or Cocoon than, for example, a pure MS shop.
If you go with something like Cocoon you have, in turn, the ability to
easily do SAX pipelines. That then means that you can easily do
multiple transformations (breaking down the cacheable vs.
non-cacheable portions of the site as appropriate) which in turn means
your XML architecture can be more granular and also makes it easier to
use multiple vocabularies. An example Cocoon site doing lots of
content through Cocoon is www.vnunet.com which might be somewhat close
to where you're headed? (Note it's being served out of Italy,
depending on where you're located you may get a bit of latency...)

Do you intend to stick with PHP and mySQL/postgress on the back end? 
Do you intend to shred your XML or can it be treated as opaque blobs
(IE; is it pure content or are you driving other business logic)? From
what I recall there are a lot of entries in the PHP side for XML
management.  I take it none of them come with any XML models that you
feel are appropriate to your needs?  Are there any industry specific
XML vocabularies that you must (or would like to) support?

I wonder, it sort of sounds like you are having a go at building your
own CMS solution.  Which raises the question of whether you've looked
at any of the pre-packaged solutions (proprietary or Open Source)?  
It's still really hard to tell what your real needs are, a bit more
explanation of the business side might help...

Peter Hunsberger


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS