SourceForge : Post

Project: Editor Discussion > INFO:GridCPR Use Cases > 2) Checkpoint data management. > List of Posts

Forum Topic - 2) Checkpoint data management.: (5 Items)

View: as

10/18/2005 10:35 AM

post4717

2) Checkpoint data management.

On half of Guru Prasad <guru_bn@yahoo.com>,

2) Checkpoint data management. Once the checkpoint data has been
created, it needs to be managed. For example, there needs to functions
for deleting checkpoint data that is no longer needed. Also, this API
should provide a mechanism for querying the meta-data that is associated
with checkpoint data.

I understand that Checkpoint has to be stored somewhere to be able to
delete or query the meta-data. It is said tacitly in the above
paragraph. But I feel we have to define the storage of checkpoint also
as this is a big question in its own. This will have implications on
Authentication, Authorization, Accounting, and also maintain the Data
Integrity.

Paul Stodghill

10/25/2005 9:23 AM

post4718

Re: 2) Checkpoint data management

On half of Guru Prasad,

I think we should mention about the storage model atleast as a part of Checkpoint Management component of Figure 1. 
Though it is implied in the existing document, I think mentioning it will make it more clear.

Paul Stodghill

10/25/2005 9:32 AM

post4720

Re: 2) Checkpoint data management

I apologize, but I still don't understand what you are suggesting. Do you think that there is a particular storage model
 that is implied by the use-cases? Can you give an example of the sorts of changes that you think should be made to the 
use-case doc?

Thanks for your comment.

Paul Stodghill

10/21/2005 8:30 AM

post4719

Re: 2) Checkpoint data management.

I agree that we need to define it, but do we need to do so in the Use-Case document? Do you see any requirements that 
are missing or would be more clearly specified if we defined a storage model more clearly in the Use-Case document?

Thanks for your comment.

Andre Merzky

03/15/2007 9:55 AM

post5767

Re: 2) Checkpoint data management.

> I agree that we need to define it, but do we need to do so in the Use-Case 
> document? Do you see any requirements that are missing or would be more 
> clearly specified if we defined a storage model more clearly in the Use-Case 
> document?
> 
> Thanks for your comment.


Addressed by changing text to:

  Checkpoint data management.
  Once the checkpoint data has been created, it needs to be _s_t_o_r_e_d_ _a_n_d_ managed. 

(underlined text inserted)

Return