Thanks, Bill! This is very helpful! On Wed, Sep 21, 2016 at 7:44 AM, <open-ils-dev-requ...@list.georgialibraries.org> wrote: > Message: 5 > Date: Wed, 21 Sep 2016 10:44:38 -0400 > From: Bill Erickson <beric...@gmail.com> > To: Evergreen Development Discussion List > <open-ils-dev@list.georgialibraries.org> > Subject: Re: [OPEN-ILS-DEV] Which OpenSRF gateway should I use? > > > Hi Jane, > > I can say unequivocally that you should not use /gateway. The weird /* */ > doodads are not valid JSON. I'll open a LP bug for deprecating this. > > /osrf-gateway-v1 is fine. I see no reason that it won't be around for the > foreseeable future. This interface uses a layer of abstraction one step > above OpenSRF, though. It does not support streaming responses or OpenSRF > sessions (useful for client-driven DB transactions). The beauty of this > interface is that it's simple to test in a browser (as you have found). > > /osrf-http-translator provides a lower level OpenSRF API and supports > streaming responses, but its use is no longer encouraged, because the > underlying mechanism (multipart/x-mixed-replace) is deprecated and only > works with our old version of XULRunner. This interface will likely be > deprecated along with the XUL client. > > /osrf-websocket-translator (from newer versions of EG/OpenSRF) provides a > standard OpenSRF API, streaming responses, etc. It's new enough, though, > that it's not universally deployed. > > WebSockets install docs: > http://evergreen-ils.org/documentation/install/OpenSRF/README_2_4_1.html#_optional_websockets_installation_instructions > > Hope this helps, > > -b >
-- Jane Sandberg Electronic Resources Librarian Linn-Benton Community College sand...@linnbenton.edu / 541-917-4655