RE: Server Side Magic.

All,

The Model View Controller pattern provides an excellent solution to this
design issue, indeed I'd call it the 'standard solution' to this problem.

This is just one link,
 
http://java.sun.com/j2ee/blueprints/design_patterns/model_view_controller/in
dex.html

a search for 'Model View Controller' in you're favourite search engine
should turn up a lot more articles.

Martin Spamer
Senior Software Engineer
Kingston Communications
Phone +44 (0) 1482 602 670
Fax +44 (0) 1482 602 899
E-Mail martin_spamer@kingston-comms.co.uk
<mailto:martin_spamer@kingston-comms.co.uk> 
http://www.kingston-comms.co.uk/ <http://www.kingston-comms.co.uk/> 


	-----Original Message-----
	From:	Tomas.Majak@speedytomato.net
[SMTP:Tomas.Majak@speedytomato.net]
	Sent:	18 June 2001 18:06
	To:	jvierine@mail.niksula.cs.hut.fi; www-mobile@w3.org;
www-tv@w3.org
	Subject:	RE: Server Side Magic. 

	Hi Juha,

	I am not quite sure if I follow you all the way, but it seems to me
as if
	you could take another approach;

	Firstly you could determine basic information from the client, such
as which
	ML it uses. From there moving on to display and memory capabilities.
Once
	these are determined you could produce XML according to the memory
	limitations. This XML which now is fitted for the memory
capabilities of the
	terminal could then be parsed to the ML that the terminal supports
according
	to it's CC/PP. Then continue with tweaking the content of the ML in
order to
	make it fit the display, e.g. choose color depth and size of images.


	This could all be done with rules for selecting the content and
	parameterized functions which produce it.

	Hope I made my self clear.

	Kind regards

	Tomas Majak

Received on Tuesday, 19 June 2001 05:18:15 UTC