Paul, is makeRequest is in osapi.http currently, or is that still a "to do"?
On Mon, May 2, 2011 at 1:39 PM, Paul Lindner <[email protected]> wrote: > The whole point of osapi is to make the rest/json server-side > APIs orthogonal with the javascript API. > > Unless you have special cases I'd suggest sticking with osapi for as long > as > you can. > > (reminds me that I need to re-implement makeRequest on top of osapi.http) > > On Mon, May 2, 2011 at 10:01 AM, Davies,Douglas <[email protected]> wrote: > > > We are adding a new service to our shindig server. After reading this > > article > > > > > > > > http://www.dr-chuck.com/csev-blog/2010/07/sending-data-to-a-server-side- > > service-with-shindig/ > > > > > > > > it appears to me that the service is then exposed through osapi. > > However... is this the interface we should be exposing to our clients or > > is it best practice to wrap the calls in a feature? It seems that > > towards the end of the article that's exactly what he does. We are also > > thinking of extending the common container and exposing the new service > > through a feature that provides those extensions. Do we help/hinder > > ourselves in either scenario? > > > > > > > > Doug > > > > > > > > > > > -- > Paul Lindner -- [email protected] -- linkedin.com/in/plindner >
