namedgraph commented on PR #3184: URL: https://github.com/apache/jena/pull/3184#issuecomment-3293997485
@Aklakan I understand the need for a proxy but I'm not convinced it should live in a `Dataset` implementation. It might feel that way because many of Jena's core classes unfortunately conflate the domain model implementation with the transport details - which are orthogonal concerns IMO. I know I've said this before, but this much more cleanly separated in JAX-RS. Conceptually the proxy is not of a _dataset_ - it is of an _endpoint_. A dataset should not care where it came from - it's just a bag of quads. To illustrate, this is a SPARQL endpoint implementation in JAX-RS. The separation of concerns is much cleaner IMO. https://github.com/AtomGraph/Core/blob/master/src/main/java/com/atomgraph/core/model/impl/SPARQLEndpointImpl.java It can use an different `EndpointAccessor` implementations - one based on a `Dataset` and one for remote endpoints. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
