Tom Weiss wrote:
Michael,

I have two points on this

Firstly, my experienc with Cocoon is that it can be really slow for dynamic publishing, especially when you have multiple XSLT transformations. Don't you think this would quickly get too complicated for the platform.
Well, the current XSLT processors used by Cocoon have improved a lot
and became pretty fast, but it certainly depends on your application.

I guess in your case (personalized content for mobile phones) there won't be large documents and probably not that many XSLT transformations ;-) Depending on content you can also probably do a lot of caching.
Load Balancing might also be an option.


Secondly, what sort of data model would you use? I guess you are talking about some kind of XSLT which applies device specific delivery rules across the whole sitemap to decide what is rendered...
Cocoon has the principle of matchers and selectors, where different "requests" can be mapped on different pipelines. This has nothing to do
with XSLT, but then of course based on this "mapping" different XSLTs or other kind of transformers will be applied in the end.


the problem is
that you have some software development to do everytime a new handset is rolled out
Well, I guess that will be inevitable, at least you have to do some regression tests. But you probably won't have to change anything at your data model and at your "Java classes", only within XSLTs and within your
Cocoon sitemap (pipelines,etc.)

and how can you be sure that you have enough fields in your
content to ensure that you will be able to build appropriate rules for new handsets as they are made available...

Well, that's the power of XML (eXtensible Markup Language ;-)

But I have to admit in oder to make a really serious statement I would have to see the specification of your "portal for mobile phones".

In case you are interested, then we might better discuss this off the mailing list.

Thanks

Michael




t.

P.S. I'm beginning to see why CMSs don't support this kind of thing out of the box.

Michael Wechner wrote:

Gevers, Julian wrote:

Tom,

I've come across the following systems for doing this :

www.volantis.com
www.wokup.com

No doubt there are others. They are not CMSes, but deliver CMS content to
mobile devices.
I have not yet come across a CMS that provides the functionality that these
mobile delivery systems do.


In think there are some (at least in the case of Open Source ;-): You just take any system which is really capable of handling XML, XSLT and Pipelines. I am pretty confident that the principle of Cross-Media Publishing can also be applied to Cross-Mobile-Device Publishing.

Thanks

Michael



HTH,
Julian

-----Original Message-----
From: Tom Weiss [mailto:[EMAIL PROTECTED]] Sent: 11 December 2002 20:53
To: cms-list
Subject: [cms-list] CMS and mobile handsets


I've been working on a really tricky CMS problem recently: basically if you run a large mobile portal you end up have to support a wide range of mobile phones (100+) and not all pages will work on all phones. For some, this is simply a case of the content not being appropriate, i.e. Club Nokia on a Motorola phone, some it relates to downloading paid for content that doesn't work on your phone (ringtones, java games), or may even be dependant on multimedia features on the phone (i.e. colour).

Basicaly you end up with a massive range of different sitemaps - almost one for each phone - whereas what you really want is a single sitemap and rules to define what pages are shown to different groups of phones.

Now - I've stated the requirement, which is half the battle - but as you know I am a great fan of using CMSs "out of the box" with as little customisation as possible, so what I'm wondering is
a) Does anyone know of a commercial CMS that can do this? (Vendors, this is not an invitation to spam me - if you system does it, then post to the list the name of an example site that is using your CMS out of the box for this application).
b) Is there another way to approach this problem that results in a solution without massive customisation to the CMS?

Cheers,

Tom.

--
http://cms-list.org/
trim your replies for good karma.


This email and any attached files are confidential and copyright protected.
If you are not the addressee, any dissemination of this communication is
strictly prohibited. Unless otherwise expressly agreed in writing, nothing
stated in this communication shall be legally binding.


--
http://cms-list.org/
trim your replies for good karma.



--
http://cms-list.org/
trim your replies for good karma.



--
http://cms-list.org/
trim your replies for good karma.

--
http://cms-list.org/
trim your replies for good karma.

Reply via email to