[Seaside] rails niceties equivalents?

Sebastian Sastre ssastre at seaswork.com
Sun May 17 16:04:05 UTC 2009

> I don't think it's that simple and I don't think we should discourage
> people who want to work on this. 

+1. that's the easy way. That would be a shoot in the foot with cannon. Pretty
much as the experience of kicking in the ass your customers. Not an attitude to
talk well about.
> Seaside has always been capable of supporting other paradigms, though
> this should be more obvious again with the reorganization in 2.9. At
> its core, Seaside is a request and response dispatching engine. So
> while you are right that Seaside is not *currently* a RESTful
> framework, it wouldn't take much effort to make it support both a
> Rails-type model and the existing Session model if only someone knew
> what they wanted a request handler for the former to look like. And I
> think being able to easily develop stateless rails-style apps with
> full REST URLs but using the Canvas API would be a huge win for many
> people.
Absolutely and the core dev team should not feel pressure about this. I bet it
can be made as a Seaside add on that any other framework familiarized developer
can do and be kind enough to share under a MIT kind of license.


More information about the seaside mailing list