ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bram de Kruijff (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACE-402) Change file repository layoout and prefs usage
Date Mon, 05 Aug 2013 10:37:47 GMT

     [ https://issues.apache.org/jira/browse/ACE-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Bram de Kruijff updated ACE-402:
--------------------------------

    Description: 
ACE-391 added optional configuration to the file repositories, but there are still two concerns
that I would like to address which are not strictly backward compatible.

1) The RepositoryFactory assigns working directories based on the PID which is a hard to interpret
randomly generated number. As we have logical concepts as 'customer' and 'name' for repositories
I suggest to use those (in a fs safe fashion) instead.

Eg.

current layout       : <basedir>/<pid>/<revision><extension>
proposed layout   : <basedir>/<customer>/<name>/<revision>[extension]

2) The RepositoryFactory uses prefs (keeping unsafe refs which is a bug) for, AFAICS, the
sole purpose of guaridng uniqueness of customer/name combination. Addressing the layout as
described in 1 voids the need for prefs altogether so I ould like to remove it.






  was:
ACE-391 added optional configuration to the file repositories, but there are still two concerns
that I would like to address which are not strictly backward compatible.

1) The RepositoryFactory assigns working directories based on the PID which is a hard to interpret
randomly generated number. As we have logical concepts as 'customer' and 'name' for repositories
I suggest to use those (in a fs safe fashion) instead.

Eg.

current layout       : <basedir>/<pid>/<revision><extension>
proposed layout   : <basedir>/<customer>/<ame>/<revision>[extension]

2) The RepositoryFactory uses prefs (keeping unsafe refs which is a bug) for, AFAICS, the
sole purpose of guaridng uniqueness of customer/name combination. Addressing the layout as
described in 1 voids the need for prefs altogether so I ould like to remove it.






    
> Change file repository layoout and prefs usage
> ----------------------------------------------
>
>                 Key: ACE-402
>                 URL: https://issues.apache.org/jira/browse/ACE-402
>             Project: ACE
>          Issue Type: Improvement
>          Components: Repository
>    Affects Versions: 1.0.0
>            Reporter: Bram de Kruijff
>
> ACE-391 added optional configuration to the file repositories, but there are still two
concerns that I would like to address which are not strictly backward compatible.
> 1) The RepositoryFactory assigns working directories based on the PID which is a hard
to interpret randomly generated number. As we have logical concepts as 'customer' and 'name'
for repositories I suggest to use those (in a fs safe fashion) instead.
> Eg.
> current layout       : <basedir>/<pid>/<revision><extension>
> proposed layout   : <basedir>/<customer>/<name>/<revision>[extension]
> 2) The RepositoryFactory uses prefs (keeping unsafe refs which is a bug) for, AFAICS,
the sole purpose of guaridng uniqueness of customer/name combination. Addressing the layout
as described in 1 voids the need for prefs altogether so I ould like to remove it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message