[Registry-dev] Resource lifecycle handling

[Glen Daniels]

Hi Deepal!

Deepal Jayasinghe wrote:
>> I was thinking that changes could occur while the resource was in the 
>> "ready for review" state (you could also think of that as "in review") 
>> - it might go through several versions before passing review, but once 
>> reviewed there still might not be an explicit copy to a new path.  So 
>> it's not changes to content that I'm calling "copies", it's changes to 
>> the path.  In any case, I'm glad we agree about the possibility of 
>> state changes where nothing else changes.
> I agree with you in this , but for easy of development point of view and 
> version point of view I think if we make a deep copy of the resource 
> when state changes will be very useful.

Could you explain a little more here?  I don't see how it makes 
development any easier to copy every time there's a transition - a 
transition, as I see it, just calls some code which can do whatever it 
wants.  Copying is simply one of the common things that code might (or 
might not) want to do.  Yes, we should provide examples and 
out-of-the-box functionality for copy-on-transition, but I don't think 
we should bake it in.

>> Hm, well the same point [reserving parts of the namespace] applies
 >> at the top level doesn't it? :)
> Well not really , or we can enforce user not to do that.

I'd rather give them the choice, like we give them the choice where to 
put their WSDLs.  Any given way we might constrain users into doing this 
would be inappropriate for someone out there, IMHO.

>>> Its depend on the way you identifying the resource , if we going to 
>>> identify the resource be its path then resource can have only one 
>>> state at any given time.
>>
>> Not in the model I suggest.  Since each lifecycle can potentially use 
>> a different property or properties to represent its "state", a given 
>> resource can be in many states at one time.  
 >
> Will that be a practical use case , I mean one resource in a number of 
> lifecycle states.

Sure - for instance, every resource on the system might be in a 
lifecycle involving editorial review to watch for spelling and profanity 
which has "needs-review" and "ok" states.  In addition, different 
departments might have their own development lifecycles of the 
built/tested/deployed variety.

--Glen