On Tue, Aug 22, 2006, EV wrote:
> > has changed. This can be fixed if we have a flag which gets set
> > when the properties change. I implemented this fix last night
> > and it seems to do the job, although I haven't done much
> > testing yet.
> 
> It does not matter for riocp, as all the writting operations are 
> made in a batch after grabbing the write lock lock.

It does matter. riocp now *always* grabs a write lock, whereas before
it would only grab a write lock if there was something that needed
to be written.

> > I will need help to implement this as the ethernet protocol
> > does not seem to be particularly well documented with respect
> > to i/o locking.
> 
> Moreover, you'll need a RK with a working Ethernet interface ;)

That's what I meant. Since the only way of working out which calls
need locking is by trial and error, I can only guess. Other people
will have to test.

Keith.

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
linux-karma-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-karma-devel

Reply via email to