[jira] [Commented] (JENA-1248) Support multiple embedded Fuseki2 servers running in the same JVM (on different ports)

[ https://issues.apache.org/jira/browse/JENA-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15588223#comment-15588223 ] Andy Seaborne commented on JENA-1248: - Embedded Fuseki does not use shiro. Embedded Fuseki is

Re: RDF Patch - experiences suggesting changes

On 14/10/2016 17:09, "Andy Seaborne" wrote: I don't understand what capabilities are enabled by transaction granularity if there are multiple transactions in a single patch. Concrete examples of where it helps? However, I've normally been working with one

[GitHub] jena issue #180: JENA-1248: Fuseki registry update

Github user rvesse commented on the issue: https://github.com/apache/jena/pull/180 Looks good to me My only concern is how Shiro behaves in a environment where each invaded server may have a different security configuration. --- If your project is set up for it, you can

[jira] [Commented] (JENA-1248) Support multiple embedded Fuseki2 servers running in the same JVM (on different ports)

[ https://issues.apache.org/jira/browse/JENA-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15588178#comment-15588178 ] ASF GitHub Bot commented on JENA-1248: -- Github user rvesse commented on the issue:

Re: RDF Patch - experiences suggesting changes

I had a quick go, and the penalty from gzip with using expanded forms without "R" was negligible (~ 0.1%, a bit higher with no prefixes). It also means you can't process the RDF Patch in a parallel way without preprocessing. (Same for prefixes). Using "R" could also restrict possible compression

[jira] [Commented] (JENA-1248) Support multiple embedded Fuseki2 servers running in the same JVM (on different ports)

[ https://issues.apache.org/jira/browse/JENA-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15588167#comment-15588167 ] Rob Vesse commented on JENA-1248: - Doesn't the Apache Shiro Library assume that the Security manager is a

Re: RDF Patch - experiences suggesting changes

Yes but ANY is a form of lossy compression. You lost the actual details of what was removed. Also it can only be used for removals and yields no benefit for additions. On the other hand REPEAT is lossless compression. However if you apply a general-purpose compression like gzip on top of the

[GitHub] jena issue #180: JENA-1248: Fuseki registry update

Github user afs commented on the issue: https://github.com/apache/jena/pull/180 Embedded Fuseki does not use Shiro. Fuseki (full) uses Shiro setup via the servlet context (not that Fuseki)full is aimed at multiple servers per JVM: better either 2 ports, one server, one JVM

[GitHub] jena pull request #180: JENA-1248: Fuseki registry update

Github user asfgit closed the pull request at: https://github.com/apache/jena/pull/180 --- 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

[jira] [Commented] (JENA-1248) Support multiple embedded Fuseki2 servers running in the same JVM (on different ports)

[ https://issues.apache.org/jira/browse/JENA-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15588727#comment-15588727 ] ASF subversion and git services commented on JENA-1248: --- Commit

[jira] [Resolved] (JENA-1248) Support multiple embedded Fuseki2 servers running in the same JVM (on different ports)

[ https://issues.apache.org/jira/browse/JENA-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne resolved JENA-1248. - Resolution: Fixed Fix Version/s: Fuseki 2.4.1 > Support multiple embedded Fuseki2 servers

Re: RDF Patch - experiences suggesting changes

They must be in teh order presented. QD then QA is a different outcome to QA then QD. On 19/10/16 15:00, Stian Soiland-Reyes wrote: Obviously that would be the case for the flat file (no transactions) and order of any transactions. So if that is the case also *inside* a transaction, then you

[jira] [Commented] (JENA-1248) Support multiple embedded Fuseki2 servers running in the same JVM (on different ports)

[ https://issues.apache.org/jira/browse/JENA-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15588728#comment-15588728 ] ASF subversion and git services commented on JENA-1248: --- Commit

[jira] [Commented] (JENA-1248) Support multiple embedded Fuseki2 servers running in the same JVM (on different ports)

[ https://issues.apache.org/jira/browse/JENA-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15588729#comment-15588729 ] ASF GitHub Bot commented on JENA-1248: -- Github user asfgit closed the pull request at:

[jira] [Commented] (JENA-1248) Support multiple embedded Fuseki2 servers running in the same JVM (on different ports)

[ https://issues.apache.org/jira/browse/JENA-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15588726#comment-15588726 ] ASF subversion and git services commented on JENA-1248: --- Commit

Re: RDF Patch - experiences suggesting changes

On 19/10/16 11:34, Stian Soiland-Reyes wrote: I had a quick go, and the penalty from gzip with using expanded forms without "R" was negligible (~ 0.1%, a bit higher with no prefixes). It also means you can't process the RDF Patch in a parallel way without preprocessing. (Same for prefixes).

[jira] [Commented] (JENA-1248) Support multiple embedded Fuseki2 servers running in the same JVM (on different ports)

[ https://issues.apache.org/jira/browse/JENA-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15588711#comment-15588711 ] ASF GitHub Bot commented on JENA-1248: -- Github user afs commented on the issue:

Re: RDF Patch - experiences suggesting changes

I am pretty sure that the intent is that a patch must be read in linear order i.e. It is not designed for parallel processing On 19/10/2016 11:34, "Stian Soiland-Reyes" wrote: I had a quick go, and the penalty from gzip with using expanded forms without "R" was