I'm resending previous e-mail hoping someone will answer my questions :)
---
Hi,
I'd like to give you an update about progress with Erlang binding as
well as raise a question.
What's working:
1. Client RPC (invoking Erlang functions)
2. Sending Erlang messages to remote Erlang mboxes by executing methods
backed by Erlang reference bindings
3. Service RPC (exposing SCA components operations as Erlang functions)
4. Exposing SCA components operations as Erlang message boxes
5. Erlang cookies (which are something like passwords which value should
match on both communicating nodes)
6. Timeouts, which:
a. for services allows user to define acceptable time between client
connects and sends it's messages (this feature allows ie. to prevent
stealing thread)
b. for references allows to define acceptable response time
And my doubts:
For each Erlang node (which in fact is for every service binding) I'm
creating connection listener, and after establishing connection new
request is going to be handled by separate thread taken from pool. I'm
not feeling that having fixed size of thread pool is good idea, it
should be configurable to match users requirements. I'm not sure if such
option fits as <binding.erlang> attribute, if not then where such value
should be passed?
I'd also like to move this code out of the sandbox. Which branch should
I choose?
Thanks,
Wojtek
