Hey Richard, My name is Alex Karasulu. I founded the LDAPd project. From the outside in, the LDAPd site has slowed down. We've been reorganizing things a bit and reconsidering designs within the server.
Yes I too was watching Silk intently however it did not go very far it seems. I wanted initially to use it in the ldap server but found that I needed a form of SEDA more conducive to LDAPd and so devised my own interfaces. SEDA is one of those great but simple ideas that's going to go real far but there can be many ways to implement it. LDAPd as a stateful protocol server definately needs SEDA or rather non-blocking IO to be able to support thousands of concurrent clients without having a thread dedicated to each client. The server has not made the jump yet to fully take advantage of its SEDA design aspects. This is due to some issues that we have been debating like using NIO or Matt Welsh's native apis. If we use Matt's stuff then we loose the compile once run anywhere. If we use NIO then we don't have ssl. So there are many tradeoffs. We would love to have you work with us to develope the first stateful SEDA based protocol server written entirely on Java. At this point we need to further reevaluate the architecture and it is a great time for new people to get involved. I too would like to work with people at Avalon to have a generalized SEDA package but I think it will be very difficult. Might work well with a HTTP server but Silk when I assessed it presented problems for LDAP. Keep looking and keep me posted - I would love to work with you on anything SEDA based. Alex > > From: Richard Wallace <[EMAIL PROTECTED]> > Date: 2003/07/10 Thu AM 12:16:05 EDT > To: Avalon Developers List <[EMAIL PROTECTED]> > Subject: Silk status > > Hello all, > > I've been away for a while. Got caught up in some things at my (now > former) job that diverted all my time away from the projects that I had > going using Avalon. I've started a new job, am planning to open up my > own small business and am hoping to get more time to work on my own > projects. > > One thing I was just starting to research when I got diverted was SEDA. > I was very impressed with it and now that I'm going back over and > reading more of the papers on it I realize just how cool it really is. > > I remembered much talk about using SEDA as a basis for event type stuff > in Avalon. I see the Excalibur Event package and it is a good basis. > Unfortunately, it looks like development on implementing the complete > architecture in Silk has stalled or stopped all together. The last > mention of it I find on the mailing list is from nearly a year ago. > > So, I guess my question(s) are: Does anyone plan on resuming work on > Silk or has anyone privately been working on it? Has anyone even given > it any more thought and maybe would be willing to offer input if someone > were to start working with it again. > > I've seen some thoughts flying around lately about a simple HTTP server > for Avalon and this would be a great place to use the SEDA/Silk > architecture since Matt Welsh describes implements an HTTP server as a > use case for SEDA. > > I also know that there is a project on sourceforge called ldapd that is > using phoenix to provide a framework and is using SEDA for the internal > processing. I'm not sure if they were using the SEDA libs from Matt > Welshes site or not, but it is another place where an Avalonized version > of SEDA could be cool. Alas, it looks like development on that has > stalled as its activity percentile has been at 0% for a couple of > weeks. It's too bad too cause an ldap server was another thing I was > thinking of starting on before I was torn away from this stuff. > > Anyways, if anyone has any thoughts/code/whatever on the status of SEDA > and Silk let me know. I'm still going through some of the documents but > everything seems pretty straight forward. The most complicated part > seems in the monitoring and managing of resources for the stages. > > Thanks, > Rich > > > --------------------------------------------------------------------- > 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]
