Announcing the Coadunation 1.0.1 Daemon Server

coadunation writes "After more than a year's worth of development, the Coadunation project is proud to announce the first official version of the Coadunation Java-based daemon server, version 1.0.1. Coadunation enables developers to quickly and easily develop daemons, web applications, distributed applications, manage distributed services, etc. We hope to follow this release by a web site overhaul in the next two weeks, that will replace the corporate facade with a community-based Web site."

News?

[kriss]

Nothing truly original, nothing really noteworthy. I can see this on freshmeat, but - as others have stated - front page material?

If your software is good, you probably don't need to plug it on slashdot yourself in the first place.

Re:Interesting...but niche?

[Anonymous Coward]

I'm just wondering...if you wanted to build a chat server who's users were users that had already authenticated against your web site, would this be a better example of the technology?

Can't do

[Aladrin]

The FAQ page reads like a list of things it -can't- do and why some of that's great. (Simplicity)

http://www.coadunation.net/faq.php [coadunation.net]
"Yes Coadunation does allow the developer to implement threads." - No built-in support.

There are times when this type of development is not appropriate or over complicates the matter;" - Having events was too complicated

"Yes clustering is supported, but not like an application servers. A cluster of Coadunation instances do not run as one system. They are instead bound together in a hierarchy, making it possible to access any daemon anywhere in a cluster." - Not much of a 'cluster' if you have to reference each server specifically.

"Unfortunatly at this point no CORBA interceptors are available to authenticate the call on Coadunation." - That's a no.

"Coadunation does not however allow more than one endpoint per WSDL file." - If you can't handle a real WSDL, why bother?

"Is UDDI suppoted? Not at this point there are plans to implement it." - Another no.

There are a few 'yes'es here and there, but mostly it's a big negative. There's something to say for simplicity, but cutting features in a 'clustered' daemon doesn't seem to be a great idea.