[OPEN-ILS-DEV] Fastest way to load titles after catalog search (via OSRF)?

[Jason Stephenson]

On 09/21/2016 07:32 AM, Ken Cox wrote:
> Thanks, but the GatewayRequest class I am using is from a old fork.  The
> Android sources had to fork a while back because of limitations in the
> platform support.  For example, OSRFRegistry had to be made Serializable
> and the parser had to be replaced with XMLPullParser.

That is likely not a problem. There hasn't been a commit to the OpenSRF
Java code since December of 2012. Pretty much none else uses it.

If your Android changes are compatible with regular JDK versions, you
could submit them as enhancements to the OpenSRF project.

Likewise there are Java classes for Evergreen. Are you using those? If
so, have you needed to fork them?


> 
> Ken
> 
> On Tue, Sep 20, 2016 at 10:08 AM, Bill Erickson <berickxx at gmail.com
> <mailto:berickxx at gmail.com>> wrote:
> 
> 
>     On Mon, Sep 19, 2016 at 8:02 PM, Ken Cox <kenstir at gmail.com
>     <mailto:kenstir at gmail.com>> wrote:
> 
>         Bill, awesome tips, thanks!  I look forward to benchmarking them.
> 
>         In some places I am using the GatewayRequest class, but in many
>         I am using a new GatewayJsonObjectRequest class, which
>         extends com.android.volley.Request.  The volley library
>         <https://developer.android.com/training/volley/index.html>
>         launches multiple parallel requests.  
> 
> 
>     The GatewayRequest class supports multiple parallel requests as
>     well.  See the sendAsync() example in org/opensrf/test/TestGateway.java
>      
> 
> 
>         Is there a version of Evergreen that supports websockets?  (I
>         don't see any happening on CW/MARS).  There is at least one
>         active Android library for websockets, it's part
>         of https://github.com/koush/AndroidAsync
>         <https://github.com/koush/AndroidAsync>.
> 
> 
>     Any EG instance with a functioning browser client is running
>     websockets.  If they are not running the browser client, they are
>     almost certainly not running websockets.  It will be some time
>     before everyone is using it.
> 
>     -b
> 
> 
> 
> 
> -- 
> -Ken