Re: File Locking

[Arne Claassen]

you can always call flock(), although i'd use that more for preventing 
multiple writes. Generally the modify of libxml shouldn't be in place, 
i.e. it does it in memory and then does a write. Sure that's not 
atomic, but close to.

If that does concern you, write to tempfile and then use move() (from 
File::Copy) to swap out the old and new files. That is an atomic 
operation.

hth,
arne
On Jun 27, 2004, at 10:09 PM, Alex Sergeyev wrote:
Hello AxKit Users,
I looked into libxml code. There are no any filelocks... Does it mean 
that I can have problems with my AxKit application which reads XML in 
one place for site visitors and can modify them in other place for 
site admins?

How can I make workaround if yes?

Thanks in advance,
Alex.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]