[Seaside] Providing REST api

Sebastian Sastre sebastian at flowingconcept.com
Mon Dec 27 22:58:55 UTC 2010

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?

maybe sessions or tasks? (not that APIs don't have those, still...)

On Dec 27, 2010, at 8:08 PM, Philippe Marschall wrote:

> 2010/12/27 Sebastian Sastre <sebastian at flowingconcept.com>:
>> The best way is your way.
>> You can just use the #initialRequest: that is going to be received by your
>> app.
> If you don't go on and use the component in infrastructure
> (#renderContentOn:, …) this isn't really ideal. In the worst case you
> create a session that isn't ever used again. If you don't need the
> component infrastructure just using a RequestHandler or RequestFilter
> is probably the better solution.
> 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