Changes between Version 4 and Version 5 of PRO_LIB_LOCAL_CHANGE_SERVER_R0


Ignore:
Timestamp:
02/17/09 06:51:56 (16 years ago)
Author:
sriggins
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • PRO_LIB_LOCAL_CHANGE_SERVER_R0

    v4 v5  
    44 
    55= Analysis = 
    6 ^(Give as much as possible of the needed information for designing and implementing the task in the following sections.)^ 
    76 
    87== Overview == 
    9 ^(Provide a brief overview of the whole task in its first revision. Stick to the current revision of the task, but keep an eye to the whole task progress, and stay alert for possible smells.)^ 
     8 
     9Provide a local change server.  Simulate multi-user actions and if possible get the concept about how we're going to deal with collaboration. 
     10 
     11Common approach is to have remote proxy objects, when you set them and the server recieves it.  Instead of this, we won't have proxy objects, but real objects. We won't transfer just the values, we'll transfer changes, instead of setting the frame to 5, we'll have a change server that will collect the changes and periodically sync the changes. 
     12 
     13Change server is on client and server, merges changes.  This task is the server that is on the client, should work without internet connectivity. 
     14 
     15Modify resource, it generates changes, the change manager adds them to the change server. 
     16 
    1017 
    1118== Task requirements == 
    12 ^(List the necessary requirements that the task must fulfill.)^ 
     19 
     20 * Create a local client change server module 
     21 * Allow changes for resources to be registered with the change server 
     22 * Allow for connections between change servers (remote change servers) 
     23 * Provide a mechanism for connected servers to sync their changes 
    1324 
    1425== Task result == 
    … …  
    1627 
    1728== Implementation idea == 
    18 ^(Provide some rough implementation idea(s).)^ 
     29 
     30 * Determine if the change server should record all changes, or if the user needs to specify the use of the change server 
     31 * Connection to a remote server should be book specific. 
     32 * Connecting to a remote server may cause the connection to the local server to be implied 
     33 * All changes go through the local server, which are then synced to the the connected remote server.  This allows for offline editing 
     34 * Maybe this is a book property edited via some book settings 
     35 * Pay attention to how changes should be coalesced, if at all.  (for example if the user sets the frame size 50 times, there should only be one change record for the frame size) 
    1936 
    2037== Related == 
    … …  
    2340 
    2441== How to demo == 
    25 ^(Provide instructions for demonstration of the task.)^ 
     42 
     43Show the change log generated by the change server. 
    2644 
    2745= Design = 
    … …  
    3553 
    3654= Comments = 
    37   provide a local change server 
    38   simulate multi-user actions if possible 
    39   get the concept about how we're going to deal with collaboration 
    40   common approach is to have remote proxy objects, when you set them and the server recieves it 
    41   instead of this, we won't have proxy objects, but real objects.  We won't transfer just he values, we'll transfer changes, instead of setting the frame to 5, we'll have a change server that will collect the changes and periodically sync the changes, change server is on client and server, merges changes, this is the server that is on the client, should work without internet connectivity.   
    42   Modify resource, generates changes, change manager adds them to the change server