Locking? (was Re: [Fsp-devel] pyfsp: fspclient.connect())

[Geoffrey T. D. <da...@da...>]

On Fri, 2004-12-17 at 02:52, Radim Kolar SF.NET wrote:
> should not use get version command for detection of connected server.
> may fspd has this command disabled, lamer fspd has this hardcoded.
> Try getpro / or stat / instead.
> 
> I will use stat / in C fsplib for this purpose.

Thanks.   

I'm very busy (and/or out of town) until after New Years, but 
I will get to it in early January.

(Perhaps a note in PROTOCOL.txt on the subject is in order?)

> I will work on fspclient a little. It needs to synchronize
> locking code with FSP. If python supports access to SysV IPC shared
> memory and semap, then jeff should add locking to pyfsp also. Java
> can't do that.

Perhaps it's too early in the morning for me, but can you explain
what the locking (on the client side) is for?

Stock python does include mmap support (on systems which support
it).  There is also threading support support, but at a fairly
high level.  I don't think there is access to the lower-level pthread
interface from python so I'm pretty sure you can not use
a semaphore in shared memory (without writing a custom
extension module --- which I suppose could always be done),
if that's what you mean by 'semap'.

All of this, of course, limits portability of the code, which is
probably a bad thing.

Happy Holidays!

Jeff