Re: [Exist-open] limit file system access ?

[Pierrick B. <pie...@fr...>]

Hi,

Wolfgang Meier a =E9crit :

> Maybe I'm just too tired, but this discussion scares me.

I don't think it's worth being scared :-)

> eXist's primary purpose is to query resources stored in the database. T=
o be
> standard compliant, we have to allow external URIs to be passed to the
> doc() function, but this should not become the standard use case and
> is not recommended (for performance reasons).

Sure. I also agree with this principle.

> Adding a further abstraction to doc() or document-uri() would probably
> just cost performance. If you really need it, I would definitely
> prefer a configuration option to disallow access to external URIs.

I'm not sure it would cost so much performance but it would allow to=20
have more control over URIs in particular with relative ones. Some eXist=20
users have huge difficulties with them... and eXist itself doesn't=20
always show to be consistent in this area.

Of course, if particular URLs have to be blocked, it would be the=20
perfect place for acting ; not sure it would be so simple with the=20
current design (how many functions would need to be touched ?).

>>> Can the update extensions write to the file system?
>> Nothing prevents you to write their result to the file system...
>=20
> Err, the update extension is used to modify documents stored in the
> database. It cannot directly operate on documents in the file system.

Yes, of course.

Well, all this remains pretty theoretical until now :-)

Cheers,

p.b.