Thanks, that is very helpful. As far as event driven programming. I was thinking of something seda like. basically, I don't want to have a ton of threads waiting around for io and lock contention. Instead, I like the idea of handing off blocking tasks to an asynchronous interface for processing and to get some sort of continuation when things can move along. This works really well for async io and batching of work.
So are the cornerstone interfaces still in the plan for the future? Stuff like the socket manager etc. I'm just feeling around in the dark here but... When I write a server I like to use nio so that I can manage thousands of client connections with a small number of threads fairly. Would my socket manager just be another component managed by the container(merlin) or is there some magic for this. Does cornerstone have anything to do with all this? (I hope I'm not killing you). Thank you so much for your help and patience. Cheers, Steve -----Original Message----- From: Stephen McConnell [mailto:[EMAIL PROTECTED] Sent: Thu 11/6/2003 4:41 PM To: Avalon framework users Cc: Subject: Re: [newbie]Event based programming Steve Harris wrote: >I'm still working out in my head what all of the different pieces of >this project are and how they fit together(are phoenix and fortress >going away?). > You like asking politically loaded questions! I just want to state that the following remaks are mine alone. 1. phoneix is dead - its not going - its gone 2. Fortress 1.0 needs to bring itself up-to-date with meta and if it does not it will die >I believe that Excalibur supports event based programming but I'm >unclear what excalibur is and how it fits in with everything else. >It seems to me that Merlin is the container of choice moving forward? > Merlin is getting a lot of attention - but Merlin does not provide the event based programming model your describing. It could - that's mostly a matter of people with the need making it happen. The big plus about Merlin (and the big minus) is that Merlin is in beta - it is changing. The real imporant thing is not to loook too much at which container - instead - look at the core avalon facilities. Today that means avalon/framework and avalon/meta. I hope to see that evolve progressively - for example I would consider avalon/repository as a candidate for a facility that is a part of our core facilities. What is in Avalon core is what matters - the rest is transient. >If that is true, can event based programming be done in merlin? > Ineed more context to give you an answer. There is a terribly easy *yes* because anything can be done in Merlin - but to give you a real answer I need a bunch more information about what you want to do and the relationship concerning container/component contract. Cheers, Stephen. >I'll apologize in advance if this question seems confusing. I am very encouraged >by the parts of this stuff that I understand such as life cycle but I think >I need more help in understanding which layers things like the threading model >and socket management fit in the avalon/merlin world. > >Thanks in advance. >Steve > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > > -- Stephen J. McConnell mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- 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]
