[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[news.eclipse.technology.corona] Thoughts on corona

Per Marcin's request ...


Could you maybe send the email to the newsgroup? We would have the thread in archive, which might be useful in future for others.


It is the end of my business day now (I'm in Europe/Poland). I'll respond tomorrow.

But in short. Your understanding of Corona is more or less accurate. And I'm really impressed that you could catch it from this description! The new one is being in preparation... hope to have it soon.

BTW. We do integrate with Buckminster :)

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