1

Topic: epoll+behavior tree+disruptor

I do unusual (refactoring from naive synchronous TCP the protocol): the logic of the network protocol is spliced from cubes behavior tree in "control flow", a selector cycle epoll (Java Selector) in its own flow-singltone, N clients cause service and are locked before the transaction termination. For at least date transmission from a cycle epoll I want to use disruptor one-to-many. Who has usage experience disruptor together with epoll? Who has a cooking experience behavior tree? PS classes for behavior tree .

2

Re: epoll+behavior tree+disruptor

Hello, Mr Bombastic, you wrote: MB> I Do unusual (refactoring from naive synchronous TCP the protocol): the logic of the network protocol is spliced from cubes behavior tree the Unknown animal acquires lean  by cutting  ideas: left in code Mina (which epoll), dislocated a brain from transposition Disruptor+Behavior Tree and threw out Disruptor; inter-thread remained on not orthodox wait/notify/volatile.

3

Re: epoll+behavior tree+disruptor

Hello, Mr Bombastic, you wrote: MB> PS classes for behavior tree  itself. How it generally should work in a sheaf?

4

Re: epoll+behavior tree+disruptor

Hello, Kernan, you wrote: MB>> PS classes for behavior tree  itself. K> as it generally should work in a sheaf? Behavior Tree it is twisted in own cycle, in own thread (). Some taskov-sequences Parallely sit from: whether "it is necessary ", "to open session TCP", "", to "download", "to close session TCP". The request comes from other thread and is locked before end (it transfers object-receiver for the data tcp);  twist the somewhere threads (in Mina) and while "in process", return the status "running".