[Seaside] Providing REST api

Sean Allen sean at monkeysnatchbanana.com
Mon Dec 27 17:15:39 UTC 2010

This includes the seaside-REST stuff which might be of use to you:


On Mon, Dec 27, 2010 at 12:06 PM, Davorin Rusevljan <
davorin.rusevljan at gmail.com> wrote:

> How do you handle situations where Seaside app needs to provide REST
> api to some other system, or framework? There seem at least 2 types of
> such situations:
> a) some foreign sytem like credit card processor, or such, needs to
> call some url on your site and collect feedback. So this call is not
> necessary releated to some Seaside session, but it needs to poke
> around the database that is used by Seaside app.
> b) Javascript widget that you use in your seaside app, like for
> instance datatables, needs to make ajax calls to your server to fetch
> some session related data, and url needs to anser for instance json
> list of particular client orders.
> What is the best way to handle such situations in your experience?
> Davorin Rusevljan
> http://www.cloud208.com/
> _______________________________________________
> 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/8a3b9479/attachment.htm

More information about the seaside mailing list