Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [corona-dev] FW: Repository Update Events
Hi Dennis,

I understand the use of URIs for Corona.  It's too bad that Corona won't support CDC 1.0/Foundation 1.0 as this does limit applicable runtimes. 

FYI, ECF IDs have other advantages...specifically a Namespace extension point that allows new Namespaces to be defined...with custom parsing rules and uniqueness constraints for instance creation (as even URIs can be limiting in some circumstances...witness the use of Strings as identifiers throughout Eclipse, etc).  And it's trivial (of course) to go between IDs and URIs in runtimes that support URIs. 

And Corona is already using IDs for connecting to ECF providers...i.e. IContainer.connect(ID,...) and sharing serialized objects (e.g. group events) among collaboration group members.

In any event (so to speak)...;-)

Scott

O'Flynn, Dennis wrote:

Scott,

 

Thanks for the suggestion.  However, the use of URIs is not an issue for Corona since it is not targeted for the CDC 1.0 / Foundation 1.0 EE.

 

Corona uses URIs throughout its collaboration framework as well as server-side SOA model (WSDM, WS-Notification, etc…).  In addition, they will also be using URIs for our semantic framework.

 

URI’s also provide us with a recognized standard for identifying an abstract or physical resource.  We need this standard to allow us to support both Eclipse and non-Eclipse components that will be participating in a collaboration solution.

 

I hope this helps to explain why we choose to use URIs for identifying resources within Corona’s server-side and collaboration frameworks.

 

From: corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Scott Lewis
Sent: Tuesday, April 10, 2007 1:59 PM
To: Corona development
Subject: Re: [corona-dev] FW: Repository Update Events

 

Hi Glenn,

One thought about this.  You might consider using an ECF ID instance rather than the URI, as the URI class is not supported on the CDC 1.0/Foundation 1.0 execution environment.

Scott

Everitt, Glenn wrote:

Here is the event message that everyone ignored ;-)

 

Glenn

 

From: Everitt, Glenn
Sent: Friday, February 16, 2007 5:18 PM
To: 'Corona development'
Subject: Repository Update Events

 

I think every Repository Update Event should include the Repository URI as well as the resource URI that triggered the Repository update event.  In addition if there is way to know the URI of the user or the tool that triggered the event I think that should be added to the event

 

For example if Harry added Sally to the Team Member Repository

 

The event should include:

 the Team Member Repository URI

 the URI for Team Member Harry (he triggered the event)

 the URI of the added Team Member Sally

 

If a new log file was added to Jackrabbit Repository by a Chat Server

The event should include

the Jackrabbit Repository URI

the URI of the Chat Server since it triggered the event

the URI of the log file that was added.

 

Any comments?

 

 


The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. 

 






 
_______________________________________________
corona-dev mailing list
corona-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/corona-dev
 

 


The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. 

_______________________________________________
corona-dev mailing list
corona-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/corona-dev

Back to the top