[Seaside] Providing REST api

[Sean Allen]

not if most of your application is a serious seaside app but you need to
provide restful access to parts of it.
which from my reading was what the OP had in mind.

On Mon, Dec 27, 2010 at 5:58 PM, Sebastian Sastre <
sebastian at flowingconcept.com> wrote:

> 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
>
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20101227/2034e0ca/attachment.htm