Github user ajs6f commented on the issue:
https://github.com/apache/jena/pull/151
@rvesse : Basically, I think we share the same picture of the situation. I
wouldn't claim that this new API presents quite the same "ergonomics" as what
we now have. I think the heart of the matter is well-expressed by your
characterization: "it replaces a nicely encapsulated API with requiring users
to directly interact with a lower level API". The question is: is that okay?
Because the concern here is HTTP/networking, and I think it's at least arguable
that HTTP/networking really isn't a concern of Jena. It's something that Jena
itself relies on a library to achieve, and I'm suggesting that we don't really
gain all that much for our users by repacking that functionality, unless it is
cheap to do and there is some kind of value we can add while so doing. (And
obviously, I don't think that's so much the case here.)
You're quite right that complex authN schemes (and forms-based stuff is a
good example) get a little more onerous for the user with this new API. I would
suggest, though, that we can mitigate that pretty well with good examples and
docs. Showing people how to get their cookie and then hand around the
`HttpContext` that holds it shouldn't be too hard. I can put myself on the hook
to write some examples in the tests (or some other appropriate place), if it
would help with your concerns?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
