Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Corona CC use cases"
(→Invoke command on server through SSH) |
|||
| (8 intermediate revisions by 2 users not shown) | |||
| Line 5: | Line 5: | ||
{{CommentBox|A simple property mechanism could be used, but some predefined and required properties would have to be defined. In other words something that would replace current mechanism. In addition it would allow change logial model without changing physical model. --''Marcin Okraszewski''}} | {{CommentBox|A simple property mechanism could be used, but some predefined and required properties would have to be defined. In other words something that would replace current mechanism. In addition it would allow change logial model without changing physical model. --''Marcin Okraszewski''}} | ||
{{CommentBox|None of use cases below show example of multiple connection configurations. Can someone give one? --''Marcin Okraszewski''}} | {{CommentBox|None of use cases below show example of multiple connection configurations. Can someone give one? --''Marcin Okraszewski''}} | ||
| + | {{CommentBox|The distinction to 'what' and 'how' is stored should be enough. 'What' is the information for the user of a repository and 'How' is the information for repository adapter. There will always be cases that require special handling by repository adapter. Imagine a Jackrabbit repository available through WebServices that stores connection parameters to CVS in which TeamRepository in XML format is stored. --''Pawel Kaczmarek''}} | ||
| + | {{CommentBox|CC requires ServiceDescriptor as another node. Now there are only RepositoryDescriptors that represent 'static' contents. The idea similar to ServiceDescriptor was rised during the meeting of Eclipse collaboration project --''Pawel Kaczmarek''}} | ||
== CVS repository == | == CVS repository == | ||
| Line 18: | Line 20: | ||
* content-type=WebPage, content-format=HTML, access-type=HTTP | * content-type=WebPage, content-format=HTML, access-type=HTTP | ||
| − | + | {{CommentBox|If display layer takes into account only content-format, we would have to use some adapter for HTTP protocol, instead of passing it directly to browser :( --''Marcin Okraszewski''}} | |
| − | + | ||
{{CommentBox|It seems to me that content-type and content-format are the same. ''--Dennis O'Flynn'' | {{CommentBox|It seems to me that content-type and content-format are the same. ''--Dennis O'Flynn'' | ||
| Line 31: | Line 32: | ||
* content-type=WebPage, content-format=HTML, access-type=CVS | * content-type=WebPage, content-format=HTML, access-type=CVS | ||
| − | + | {{CommentBox|How to display it? A single web page can be easily retrieved from repository and displayed. But what about other resources referred by the page (eg. pictures, scripts, CSS) with relative paths? Is it possible to register new protocol in embedded browser? If not (and I think it is not possible), the only solution I find would be open a local HTTP port and map all requests to proper resources in repository. --''Marcin Okraszewski''}} | |
| − | + | ||
| − | + | ||
== Team member XML in CVS == | == Team member XML in CVS == | ||
| Line 41: | Line 40: | ||
* content-type=Team, content-format=TeamXML, access-type=CVS | * content-type=Team, content-format=TeamXML, access-type=CVS | ||
| − | + | {{CommentBox|How to specify which file contains the XML? --''Marcin Okraszewski''}} | |
| − | + | ||
== Team member through WS == | == Team member through WS == | ||
| Line 50: | Line 48: | ||
* content-type=Team, content-format=TeamWS, access-type=WS | * content-type=Team, content-format=TeamWS, access-type=WS | ||
| − | + | {{CommentBox|Is there any "repository adapter" that would match ''access-type'' WS? This interface couldn't be like normal repository adapter --''Marcin Okraszewski''}} | |
| − | + | ||
== Invoke command on server through SSH == | == Invoke command on server through SSH == | ||
| Line 57: | Line 54: | ||
Solution | Solution | ||
| − | * content-type=??, content-format= | + | * content-type='''???''', content-format=RemoteCommand, access-type=SSH |
| + | |||
| + | {{CommentBox| | ||
| + | * content-format and content-type names doesn't fit :( | ||
| + | * Would adapter for SSH have the same interface as repository adapter? Seems doesn't fit well :( --''Marcin Okraszewski''}} | ||
| − | + | [[Category:Corona]] | |
| − | + | ||
Latest revision as of 11:52, 9 March 2007
The current CC def'n has 2 parameters per RD. These use cases introduce a 3rd parameter, content-format. --Dennis O'Flynn
- We need a design review to finalize the set of parameters needed for each RD.
- Could a simple property (name/value) be used to allow a variable number of parameters?
A simple property mechanism could be used, but some predefined and required properties would have to be defined. In other words something that would replace current mechanism. In addition it would allow change logial model without changing physical model. --Marcin Okraszewski
None of use cases below show example of multiple connection configurations. Can someone give one? --Marcin Okraszewski
The distinction to 'what' and 'how' is stored should be enough. 'What' is the information for the user of a repository and 'How' is the information for repository adapter. There will always be cases that require special handling by repository adapter. Imagine a Jackrabbit repository available through WebServices that stores connection parameters to CVS in which TeamRepository in XML format is stored. --Pawel Kaczmarek
CC requires ServiceDescriptor as another node. Now there are only RepositoryDescriptors that represent 'static' contents. The idea similar to ServiceDescriptor was rised during the meeting of Eclipse collaboration project --Pawel Kaczmarek
Contents
CVS repository
Checkout, modify, view, read, commit resources from CVS.
Solution:
- repository with content-type=CVS, content-format=CVS, access-type=CVS
Web page
Simply a web page.
Solution:
- content-type=WebPage, content-format=HTML, access-type=HTTP
If display layer takes into account only content-format, we would have to use some adapter for HTTP protocol, instead of passing it directly to browser :( --Marcin Okraszewski
It seems to me that content-type and content-format are the same. --Dennis O'Flynn
Not quite. If a page is JavaDoc, then the content-type would be JavaDoc (or ApiDoc), while content-format still HTML. --Marcin Okraszewski
Web page within CVS or JCR repository
Web page stored in some storage repository.
Solution:
- content-type=WebPage, content-format=HTML, access-type=CVS
How to display it? A single web page can be easily retrieved from repository and displayed. But what about other resources referred by the page (eg. pictures, scripts, CSS) with relative paths? Is it possible to register new protocol in embedded browser? If not (and I think it is not possible), the only solution I find would be open a local HTTP port and map all requests to proper resources in repository. --Marcin Okraszewski
Team member XML in CVS
A team member XML in storage repository.
Solution:
- content-type=Team, content-format=TeamXML, access-type=CVS
How to specify which file contains the XML? --Marcin Okraszewski
Team member through WS
A team member repository accessible through Web Service.
Solution
- content-type=Team, content-format=TeamWS, access-type=WS
Is there any "repository adapter" that would match access-type WS? This interface couldn't be like normal repository adapter --Marcin Okraszewski
Invoke command on server through SSH
For example run command that starts build on a server.
Solution
- content-type=???, content-format=RemoteCommand, access-type=SSH
- content-format and content-type names doesn't fit :(
- Would adapter for SSH have the same interface as repository adapter? Seems doesn't fit well :( --Marcin Okraszewski