Github user asfgit closed the pull request at:
https://github.com/apache/jena/pull/82
---
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
Github user ajs6f commented on a diff in the pull request:
https://github.com/apache/jena/pull/82#discussion_r33451617
--- Diff:
jena-fuseki2/jena-fuseki-core/src/main/java/org/apache/jena/fuseki/mgt/ActionBackupList.java
---
@@ -0,0 +1,98 @@
+/**
+ * Licensed to the
Github user afs commented on the pull request:
https://github.com/apache/jena/pull/82#issuecomment-116601250
Indeed - etags are one example of a server driven mechanism. They need more
machinery than this PR has though. HTTP headers are not always easy to deal
with in client
Github user ajs6f commented on a diff in the pull request:
https://github.com/apache/jena/pull/82#discussion_r33457733
--- Diff:
jena-fuseki2/jena-fuseki-core/src/main/java/org/apache/jena/fuseki/mgt/ActionBackupList.java
---
@@ -0,0 +1,98 @@
+/**
+ * Licensed to the
Github user yyz1989 commented on the pull request:
https://github.com/apache/jena/pull/82#issuecomment-116636657
Yeah, I agree with Rob and Andy. I do think accepting POST is necessary,
but I apologize for my negligence for HEAD. That is due to my laziness because
I took the main
Github user afs commented on the pull request:
https://github.com/apache/jena/pull/82#issuecomment-116589395
I disagree a bit about POST - yes, it's not nice REST but it is
pragmatically useful to ensure up-to-date information (the client can force it
even if the server or proxies
Github user ajs6f commented on the pull request:
https://github.com/apache/jena/pull/82#issuecomment-116597497
`POST` is one way to enable a force up-to-date`, but it should also be
possible to supply an ETag, which is a little more to the exact need. Perhaps
Fuseki has helpers for
Github user ajs6f commented on the pull request:
https://github.com/apache/jena/pull/82#issuecomment-116603288
Okay-- do you think it's worth a separate ticket and PR for some helpers
for ETags, so that future new Fuseki HTTP functions could offer them at low
cost?
---
If your
Github user ajs6f commented on the pull request:
https://github.com/apache/jena/pull/82#issuecomment-116628538
Okay, sorry to cloud the waters.
---
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
Github user afs commented on the pull request:
https://github.com/apache/jena/pull/82#issuecomment-116609093
Here, the client browser is an admin interface.The read-information
operations are not a performance pain-point.
Helpers presume how they are being used in Fuseki is
Github user afs commented on the pull request:
https://github.com/apache/jena/pull/82#issuecomment-116628492
We are agreed that it's not related to this PR. Let's discuss it on dev@
and not tangle this PR with that discussion.
---
If your project is set up for it, you can reply to
Github user yyz1989 commented on a diff in the pull request:
https://github.com/apache/jena/pull/82#discussion_r33457422
--- Diff:
jena-fuseki2/jena-fuseki-core/src/main/java/org/apache/jena/fuseki/mgt/ActionBackupList.java
---
@@ -0,0 +1,98 @@
+/**
+ * Licensed to the
Github user ajs6f commented on the pull request:
https://github.com/apache/jena/pull/82#issuecomment-116612135
I meant something as simple as a method that accepts an identifier and
response and adds the correctly-formatted tag.
---
If your project is set up for it, you can reply to
Github user rvesse commented on the pull request:
https://github.com/apache/jena/pull/82#issuecomment-116555847
+1 to the idea
The implementation seems to violate REST principles though
`POST` should be used for changing data so should not be supported for a
service
14 matches
Mail list logo
