Pawel,
Thanks – that helps me understand
better.
From:
corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Kaczmarek, Pawel
Sent: Tuesday, July 18, 2006 3:34
AM
To: Corona
development
Subject: RE: [corona-dev]
ProjectContainer Definition
The examples you gave will work
usually, however there are some special cases, which can not be described
without kind and type. What if we have teamlist and, say, tasklist. Teamlist is
available through webservices and tasklist is available through an xml file. In
the example you gave, we wouldn't know the access method to teamlist or
tasklist. We know that there are some webservices but we don't know who should
invoke them and what they give.
website and teamlist is something
that carries a business information, we treat it as kind ("contents"
may be more specific), while webservice is a general communication protocol
(type or "accessMethod"). The business information is necessary for us
to invoke classes that actually use it.
URI: http://www.eclipse.org/corona
TYPE (accessMethod): http (or "file" if we
use a local html file)
KIND (contents): website
(DESCRIPTION: Corona’s
home website)
URI: http://www.eclipse.org/corona/services
TYPE (accessMethod): webservice
KIND (contents): ??? (what methods are available here?
should it be used by teamlist, eventhandler or something else)
(DESCRIPTION: Corona’s
collaboration web services)
URI: http://www.eclipse.org/corona/team.xml
TYPE: xml
KIND: teamlist
PROPERTIES: define the location of the file (local or
remote or CVS or other ...)
(DESCRIPTION: List of Corona development
team members)
In all those cases we communicate
with http, but we use it in three different way: pass the uri as a parameter to
a window that opens a web site (in 1. example), invoke a web service (in 2.
example) and download a file (in 3. example). How should we distinguish those
cases?
Pawel
From:
corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of O'Flynn, Dennis
Sent: Monday, July 17, 2006 6:00
PM
To: Corona
development
Subject: RE: [corona-dev]
ProjectContainer Definition
The assumptions I was making were:
1. The
URI is the location of the repository
2. The
URI’s scheme would (normally) be the protocol used to interact with the
repository
3. The
Type would be additional, container context specific, details on how to use the
repository.
For example:
URI: http://www.eclipse.org/corona
TYPE: website
DESCRIPTION: Corona’s
home website
URI: http://www.eclipse.org/corona/services
TYPE: webservice
DESCRIPTION: Corona’s
collaboration web services
URI: http://www.eclipse.org/corona/team.xml
TYPE: teamlist
DESCRIPTION: List of Corona development
team members
Would you please update these 3 examples showing your assumption of
TYPE and use of KIND as well.
Thanks.
-----Original Message-----
From: corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On
Behalf Of Marcin Okraszewski
Sent: Monday, July 17, 2006 10:39 AM
To: Corona development
Subject: Re: [corona-dev] ProjectContainer Definition
Firstly, as I'm familliar with the respository definition, the URI is
intended to be an identifier which is not neccessary any access
parameter.
But still, how would we indicate for instance a Web Service call from a
XML file laying on an HTTP server? I'm affraid that some uri schemes
are
not enough.
Marcin
>Wouldn't the URI have this information based upon the URI's scheme?
For
>example:
>* http://
>* cvs://
>* jdbc://
>* file://
>
>
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.
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.
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.