Hi Ken, The /osrf-gateway-v1 endpoint provides a layer of abstraction over the OpenSRF XMPP innards, where the chunking/bundling happens. If you continue using that endpoint, you'll be fine without it.
-b On Mon, Feb 11, 2019 at 1:35 PM Ken Cox <[email protected]> wrote: > Bill, thanks for mentioning that. I don't know anything about bundling or > chunking so I am quite certain my fork doesn't have them. Are these > features required when called via osrf-gateway-v1, and where are they > described? > > Ken > > On Mon, Feb 11, 2019 at 12:22 PM Bill Erickson <[email protected]> wrote: > >> Thanks, Jason. >> >> It's also worth mentioning the Java OpenSRF libs are missing some >> new features (bundling/chunking/etc.), so in addition to updating the >> dependencies, any prospective maintainer would need to port these features >> over to make the Java OpenSRF libs compatible with modern OpenSRF. >> >> -b >> >> On Sat, Feb 9, 2019 at 10:17 AM Ken Cox <[email protected]> wrote: >> >>> Hey Jason and Blake, >>> >>> Hemlock Android uses a fork of the java libraries inside its own repo. >>> Hemlock iOS uses a brand new API implemented in Swift. As long as the >>> '/osrf-gateway-v1' endpoint doesn't change, I'm all set. >>> >>> Thanks for reaching out, >>> Ken >>> >>> On Sat, Feb 9, 2019 at 12:03 PM Jason Stephenson <[email protected]> >>> wrote: >>> > >>> > Blake, >>> > >>> > I believe that Hemlock has its own implementation. Some of the files >>> > may have been copied from the OpenSRF code at some point, but the files >>> > in the OpenSRF code are not used to build Hemlock. I could be >>> mistaken, >>> > but I'm pretty sure that Hemlock does not rely on the actual Java code >>> > from OpenSRF or Evergreen. >>> > >>> > As you said, Ken knows best, so hopefully, he will answer. >>> > >>> > Jason >>> >>> >>> >>> -- >>> -Ken >>> >> > > -- > -Ken >
