[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[news.eclipse.technology.corona] Re: Thoughts on corona
The first level of Corona is something as you say. We provide an Eclipse server environment. This contains:
- web services; to expose a service you simply need to use an extension point
- a notion of "context", where you define resources within your context (in Project scope those are CVS sources, Bugzilla, project home page, chat room, etc.); context may be in relation with each other
- eventing within the context, to notify clients that joined the context
- WSDM and JMX to manage components

The services for now are expected to be through Web Services. Eventing by default is provided by ECF for Eclipse clients (plain Java serialization is used then) or WS-Notification for non-Eclipse clients. The eventing system may be replaced with anything else, eg. JMS.

The context is supposed to carry higher level information about what and where is available within the context, so participants know where to connect, etc. For Eclipse clients there are also repository adapters that allow to access some repositories in a repository agnostic way.

Now, based on this, we build as an example a collaboration solution for projects. This is intended to be an example that is really usable in everyday development.

We haven't done any performance tests yet, so I cannot say what is the load that Corona can handle.

We do not provide alternative ways of exposing services. But I know ECF provides a way of distributed service repository, similar to OSGi one. Don't know what they use for transport.

Does it help somehow?

Marcin


Bryan Hunt wrote:

If Corona does what I think it does, I plan on using it in a production environment for an internal tool. Historically, our environment tends to break all tools that don't take scaling into account. if Corona can survive our production environment, it will be a solid product. From what I can tell, Corona is fundamentally an Eclipse server-side framework, and on top of that, you have a collaboration service for sharing workspaces. Do I have this correct? It also looks like there might be the ability to "deploy" new plug-ins as services? Communication to the services can happen from either other Eclipse clients directly, or from non-eclipse client via SOAP (web services). Am I on track? We were starting to build exactly what I've described, but if that is where Corona is headed, we would prefer to not re-invent the wheel, and simply create plug-ins (services) to be deployed in Corona.

BTW, I might suggest looking at the introduction to Buckminster. They did an awesome job with their intro, and I knew exactly what the tool did. The services based projects such as Corona, STP, ALF, etc tend to use words, phrases, and descriptions that are not easily understood by those not versed in the buzzwords. Personally, when I read about these projects, I think I have an idea as to what the project does, but I could be wrong. And, I certainly have no idea how I might use that technology in our application. If those introductions were written like the Buckminster intro, I could easily determine: yep, we need to incorporate this technology into our product, or nope, we don't need that. Just some food for thought.

Bryan