> On Feb 15, 2017, at 4:10 PM, Andy Seaborne <[email protected]> wrote: > > > Then there are a couple of comments about design and jena-ldp overall. I took > away from that that ThreadPerGraphDataset is in-progress - I think it would > be better to know it is the right design for whatever it's use case is before > putting into a jena release. It gives more freedom to change without worrying > about incompatibility. > > Once released there is an obligation which can be limiting (despite any words > around it to say "may change").
Well, the code as it stands is (I think) okay-- but where does it stand within Jena? :grin: I'm going to close that PR and move the branch over to my Github clone. There are at least two possibilities here: evolve it towards some kind of jena-ldp, or expand it to try to tackle variable lock regions and a more general in-memory multiwriter setup. Either deserve their own threads of discussion. --- A. Soroka The University of Virginia Library
