Details
-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
-
None
-
None
-
Bit Sprint 1, Bit Sprint 2
Description
After discussion of the propasal on the mailing list: http://ml.sbforge.org/pipermail/bitrepository-devel/2013-June/000324.html it has been accepted by Kåre and Eld that it would be allright to go ahead with such a merge.
The following concerns should be adressed:
- A clear migration strategy needs to be defined, and agreed on across the organizations with production repositories. A scenario could be to create an intermediate protocol version with support for both types of getting file information. This could then be implemented by the pillars. Afterwords the clients and services could be migrated and the getChecksum + getFileIDs operation could be purged from the protocol.
- It should be documented on the individual fileInfo attributes what kind of considerations should be made, like cost, permission, constraints etc.
Attachments
Issue Links
- mentioned in
-
Page Loading...
1.
|
Define GetFileInfo protocol primitive | Open | Unassigned | |
2.
|
Create GetFileInfo client library | Open | Unassigned | |
3.
|
Add support for GetFileInfo in referencepillar | Open | Unassigned | |
4.
|
Add support for GetFileInfo in SB Pillar | Open | Unassigned | |
5.
|
Add support for GetFileInfo in KB Pillar | Open | Unassigned | |
6.
|
Rewrite integrity service to use GetFileInfo | Open | Unassigned | |
7.
|
Add support for GetFileInfo in SA Pillar | Open | Unassigned | |
8.
|
Add GetFileInfo functionality to the Commandline client | Open | Unassigned |