[Pharo-users] Repeateble URLs - REST?

S Krish krishnamachari.sudhakar at gmail.com
Tue Feb 26 10:24:06 EST 2019


I would defer to Seaside experts on this, but I would say yes to Seaside
REST in general and Teapot REST otherwise if it meets your requirements . I
have not worked on them for a long time now.

On Mon, Feb 25, 2019 at 2:05 PM sergio ruiz <sergio.rrd at gmail.com> wrote:

> Gotcha..
>
> So, in Seaside, should how should I handle the routes? with Seaside REST?
>
> On February 25, 2019 at 2:56:49 PM, S Krish (
> krishnamachari.sudhakar at gmail.com) wrote:
>
> https://restfulapi.net/resource-naming/
> <https://restfulapi.net/resource-naming/>
>
> https://docs.microsoft.com/en-us/azure/architecture/best-practices/api-design
>
> Given the conflicting advices on REST, you can try and adhere to one-two
> sources of advice.
>
> ----
> peace,
> sergio
> photographer, journalist, visionary
>
> Public Key: http://bit.ly/29z9fG0
> #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV
> http://www.codeandmusic.com
> http://www.twitter.com/sergio_101
> http://www.facebook.com/sergio101
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/attachments/20190226/66c60bdc/attachment-0001.html>


More information about the Pharo-users mailing list