[Seaside] Providing REST api

Sebastian Sastre sebastian at flowingconcept.com
Tue Dec 28 09:38:52 UTC 2010

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: ?

On Dec 28, 2010, at 6:57 AM, Philippe Marschall wrote:

> 2010/12/27 Sebastian Sastre <sebastian at flowingconcept.com>:
>> Isn't seaside overkill at that point?
>> I mean, if you don't use the component infrastructure what else seaside is going to help you with?
> Not at all. You can still use your familiar request and response
> objects without locking yourself to a server or dialect, you still
> have the templating engine should you need it, you can still use the
> application/configuration infrastructure.
> Cheers
> Philippe
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the seaside mailing list