Version française
Home     About     Download     Resources     Contact us    
Browse thread
netplex multi-thread asynchronous processor for passive clients
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: -- (:)
From: Serge Sivkov <ssp.mryau@g...>
Subject: Re: [Caml-list] netplex multi-thread asynchronous processor for passive clients
So, i got my service runing, partly. Currently i'm using ORPC and
synchronius calls to my RPC server. I simply can't start async RPC
client from processor's #process:
just after:
    let clnt = Protocol_clnt.create_client
      ~esys: container#event_system
      (Rpc_client.Inet ("localhost", 9007)) Rpc.Tcp in
    Protocol_clnt.new_signal'async clnt () cb;
i see in log:
Exception File "unixqueue.ml", line 954, characters 6-12: Assertion failed
But synchronious client works.

So here is my list of questions:
- why i may not to use nice netflex message bus from processor?
- how can i to know does some objects to share same event queue or doesn't?
- why i can't start async rpc client from processor by using
container#even_queue?
  (that queue is usable from processor: i can send and receive events
by using it)
- how can i use container#send_message from processor?
  (simple call to it silently hungs container's rpc)