On Wed, Oct 5, 2016 at 9:31 AM, Rubén Navarro Piris
<
ruben.nav...@gmail.com> wrote:
> Hi!
>
> I just wanted to know why the SNARL protocol is being deprecated and the
> implications of this decision:
>
> - How will this impact the performance for small queries (the case currently
> optimised by SNARL according to the docs)?
There's unlikely to be any performance difference. The smaller
overhead of SNARL vs HTTP is usually negated by the time it takes to
complete whatever action you're performing remotely.
The SNARL protocol, released in 0.6, was originally designed for, and
limited to, the admin API where we expected that tasks like adding a
user would be very quick and benefit from the smaller overhead. While
that's still generally true, most of the time users are executing
queries in which case the evaluation time dominates performance, not
transport.
> Are there any published benchmark
> results (or technical explanation) which support the decision of dropping
> SNARL?
No.
> - Are there any plans on implementing another protocol e.g. JDBC or will
> HTTP be the only connection protocol in Stardog 5?
Stardog will support HTTP(s) and HTTP2.
Cheers,
Mike
>
> Thanks in advance!
>
> Ruben
>
> --
> -- --
> You received this message because you are subscribed to the C&P "Stardog"
> group.
> To post to this group, send email to
sta...@clarkparsia.com
> To unsubscribe from this group, send email to
>
stardog+u...@clarkparsia.com
> For more options, visit this group at
>
http://groups.google.com/a/clarkparsia.com/group/stardog?hl=en