James Carman's Introduction to HiveMind has appeared on TheServerSide.com today. James must have been working pretty hard, this final version of the article is much more in depth than the early version of the article I reviewed for him a couple of month's back.
I'm really psyched about the HiveMind community ... maybe even more so than the Tapestry community. Not to dig at the Tapestry or developer or user community, I just think that HiveMind is running truer to the ideals of an Apache open source project. I think that HiveMind started on the right foot, and has several key members who are contributing code, but also recognition (such as this article by James, who is a HiveMind committer). Perhaps its because HiveMind is a more well defined problem space than Tapestry, and started more clean and better organized. I hope to get the Tapestry project functioning as smoothly as the smaller HiveMind project some day.
Just finished reading the article; he covered a lot of ground quite nicely, but didn't even mention HiveMind's distinguishing characteristics: distributed configuration (that is, support for many individual modules) and configurations. Most of his examples could be done almost as easily in Spring (though I don't think Spring has a threaded service model). A follow-up article, perhaps?
4 comments:
I like hivemind but one area where its lacking is support for macro functional components each having their own registery. Or in english why cant we add registeries at runtime.. this allows runtime application composition strategies where a codebase is deployed as a selected or configured group of artifacts. I'm confused why this seems to be so discouraged.
Too easy to inadventently spread the FUD when writing a blog (and multi-tasking). I think I was trying to say that I didn't know if threaded was built-in, or an add on.
This is off-topic but please, who ever is in charge of this blog software, can you do some window fixing by adding the date of posting rather than just the time? Oops!!
Ahmed -- does this LOOK like the TSS complaints forum? I don't work for TechTarget or have any access to the TSS code anymore, so its out of my hands. From talking with Pat Linskey, I believe there is a tuning problem with the cache that flares up every couple of months, and it has nothing to do with Tapestry.
Post a Comment