[Seaside] Providing REST api

Philippe Marschall philippe.marschall at gmail.com
Tue Dec 28 10:46:35 UTC 2010

2010/12/28 Sebastian Sastre <sebastian at flowingconcept.com>:
> Yeah but none of those is an incredible competitive advantage either.
> What I would found interesting tough, is to use seaside where it shines: managing complex state.
> Think of the facebook API or twitter or whatever API that needs to manage authentication, session expiration, persisted stuff, etc
> All things that your fully visual seaside webapp does only in a non-visual version (just with requests).
> That would be:
> 1. seriously valuable
> 2. a common need
> Wonder if tasks can be used to control state and flux of a non visual app.
> What would they #call: ?

Well, that would certainly be doable but it would not be REST at all.
You'd use components/tasks that create XML or JSON which includes the
action URL and fields names (think AtomPub or HATEOAS).

The client would then have to parse the response for the action URL
and the callback names. Maybe you also want a specialized action phase
continuation that does not redirect.


More information about the seaside mailing list