Registrar.deregister ownership transfer about amy HOT 6 CLOSED

Hi @Luminarys,

I'm not sure I follow you here. You can transfer sockets between polls. A socket stays registered until it's deregistered. You use reregister to reuse the socket for this purpose. Note also, that you can call register, reregister, or deregister from any thread where you have a clone of the registrar.

from amy.

The issue (I think?) would be that if I have a poll on thread A, which has some socket registered to it, and I want to transfer this socket to some thread B which has its own poll. If I simply transferred the socket to B and reregistered it without deregistering it on A, would that not cause events for the socket to be reported to the polls on both thread A and B?

from amy.

Oh, I see. I never intended sockets to be moved around pollers like that. My use case is that there is a single poller, and events can be routed to different threads where the sockets live via channels. Polling eats threads since it's the only thing they can be used for, and decoding messages and doing work on that thread delays any future polling. However, that's just how I use Amy, and in no way is necessarily "the right way".

I agree that your use case is valid. I don't think you'd want the same socket registered with multiple poll threads. At least with epoll, those events would be reported to both pollers. All that being said, I don't see any real reason why the API can't be changed to just take a reference to the socket in deregister. I think that would fix things so that your use case works, and I don't believe it should cause any other problems. I just looked through git blame to see if there was a specific reason I did it that way and couldn't find any safety issues. It's probably just historical at this point.

from amy.

Unless you're already working on it then, I'll submit a PR with the appropriate changes if that's alright.

from amy.

That would be great. Much appreciated.

from amy.

Fixed by #23

from amy.