I did some benchmarks for the client/server based sword data transfer.
This is how long my function for requesting the chapter text takes in
different scenarios.
The node-sword-web-api based server runs on an AWS VM. The client (Ezra
Bible App) on my Linux laptop.
The scenarios have been si
Hi Fred!
I suppose the redundancy is a general issue of json or xml when having long
lists of elements.
Http servers and clients support gzip compression (and other more modern
algorithms). That's something I could check to optimize the data amounts
that are sent when making requests on this
I'm just a lurker here, but... even though I've dabbled in json, I gotta
say that is horribly verbose! I'd be willing to bet oh, say, fifty cents
that a slow link would perform poorly. since (as I understand it) it is the
remote server sending all that, that there'd be no way to filter out all
the
Haven't been replying since I'm busy, but this is awesome. Thank you
for actually giving my idea a shot! I'll have to experiment with it :)
On Sun, 4 Aug 2024 21:00:24 +0200
Tobias Klein wrote:
> Hi Aaron & all,
>
> so, this whole thread about SWORD over network inspired me to play
> with exist
