Thanks for your reply, see my comments inline.
Wojtek
Luciano Resende:
On Fri, Mar 20, 2009 at 9:22 AM, Wojtek Janiszewski
<[email protected]> wrote:
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?
Are there case where each different services would have different
configuration parameters for these values ? If so, attributes to
<binding.earlang> seems like a good start.
So I'll try to pick reasonable default value, allowing user to overwrite
it by attribute in <binding.erlang>.
I'd also like to move this code out of the sandbox. Which branch should I
choose?
Is the erlang binding based on 1.x (1.x branch) or 2.x (trunk) code ?
This might help answer your question...
It has been written using SCA 1.4, but does it make sense to commit it
to 1.x? I'd like to commit it to 2.x and update dependencies in code.
Shall I use tuscany/java/sca?
Btw, I noticed that *SCA Java 2.x* link on [1] page is broken.
[1] - http://tuscany.apache.org/tuscany-downloads-documentations.html
