Okay, the "comet" bit, I can see that--why conflate those? To clarify--we're going to build a comet framework _on_ diesel, but diesel itself is more of a gener

Okay, the "comet" bit, I can see that--why conflate those? To clarify--we're going to build a comet framework _on_ diesel, but diesel itself is more of a general async I/O system with cluster messaging features. We intend it to be applicable for building arbitrary networked application using similar patterns to what you'd do in erlang--message passing. We just _happen_ to be focusing on building a comet framework first and foremost on it. That will probably be called "dieselweb". So, the "comet server" portion of our framework may not, in fact, utilize any of this message-broker stuff. But other components might. We're actually going to try to build something fairly unique here, but I don't have all the details ready to put out there yet.