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....@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.sudha...@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 >
