terminology I'm going to try and ask one of my questions this way.
When I read through docs and code on all this stuff. Should I ONLY be looking at merlin and avalon and not at fortress, phoenix, and excalibur or any of the other names :-).
I am very much looking forward to contributing to this project but before I can
be of any use I feel like I need to be a good user of the project. As of now,
my company is considering using avalon/merlin as the core of our
next server product. I need to get a little further along the learning curve
before I can make a good case so I'll keep reading and asking and listening.
Thanks again! Steve
On Nov 6, 2003, at 5:41 PM, <[EMAIL PROTECTED]> wrote:
On Friday 07 November 2003 09:04, Steve Harris wrote:As far as event driven programming. I was thinking of something seda like.
One thing is fairly clear; You are not alone, and there will be progress in
this area, but perhaps not in the near future.
That said, don't be discourage, join the party and influence the development
party, maybe even help out coding.
Yeah I think we need to see many incarnations of how this is done before it can be standardized. Meaning we need to see the various user use cases. Right now LDAPd uses its own model and did not really leverage the stuff in excalibur that was at that time called Silk I believe.
Would my socket manager just be another component managed by the container(merlin)?
That's is being done with LDAPd. But in the distant future after more important things are taken care of we can begin to consolidate the use cases into a generalized Avalon API for event based protocol server developement.
Most probably. However, Merlin is flexible enough that if container support is
required (TBD) it is possible to create container extensions. ATM, though,
this is a bit of "craftmanship", and there is work going (slowly though) to
make this into more solid contracts making into Core.
That's a very interesting direction. Perhaps if I find some time I'll try to look into that.
Alex
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
