On 04/05/2016 17:37, Ian Boston wrote: > Hi, > If the File or URL is writable, will writing to the location cause issues > for Oak ? > IIRC some Oak DS implementations use a digest of the content to determine > the location in the DS, so changing the content via Oak will change the > location, but changing the content via the File or URL wont. If I didn't > remember correctly, then ignore the concern. Fully supportive of the > approach, as a consumer of Oak. The locations will certainly probably leak > outside the context of an Oak session so the API contract should make it > clear that the code using a direct location needs to behave responsibly. >
It's a reasonable concern and I'm not in the details of the implementation. It's worth to keep in mind though and remember if we want to adapt to URL or File that maybe we'll have to come up with some sort of read-only version of such. For the File class, IIRC, we could force/use the setReadOnly(), setWritable() methods. I remember those to be quite expensive in time though. Davide
