hi, yes, i could have made it a service, but then i get to use the hellishly ugly tapestry urls :)
btw, the urls are still my main concern with tapestry - i think it makes it a bad choice for a public site. let's say you have a store - ideally you want to have urls like http://foo.net/products/food/fruit/apple - something that users can look at and not puke. users do navigate using the urls. this is less of a problem for internal applications, admin interfaces, etc. best regards, viktor On Thu, 12 Dec 2002 23:22:36 -0500, "Howard M. Lewis Ship" <[EMAIL PROTECTED]> said: > Shouldn't need a servlet, this is what Tapestry engine services are for. > You could define an rss service that returns text/xml (or whatever the > correct markup is). > > ----- Original Message ----- > From: <[EMAIL PROTECTED]> > To: "Roberto Saccon" <[EMAIL PROTECTED]>; "Tapestry Developers" > <[EMAIL PROTECTED]> > Sent: Thursday, December 12, 2002 8:23 PM > Subject: Re: [Tapestry-developer] Tapestry and RSS > > > > > > i'm sorry, but this part (exporting rss) has nothing to do with tapestry, > > it's just a plain servlet :) > > -- [EMAIL PROTECTED] -- http://fastmail.fm - Access your email from home and the web ------------------------------------------------------- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
