All,
Further to my actual playing with some early implementations, myself and Tim
Brody have today extended early ideas to be closer to the Google Docs
extensions and thus produced a client as a test of the implementation.
The whole thing is best demonstrated by the video which is here:
http://www.eprints.org/software/training/3.2/videos/swordv2_eprints.ogv
Things we have working:
CREATE : Initial create of the object
RETRIEVE: Obviously
UPDATE: 2 way update between both client and repository
DELETE: Again 2 way.
Additionally, Metadata can be updated to the edit-uri (also demonstrated).
All of this uses the Edit-URI, Atom:ID and Edit-Media URIs only + the contents
URIs for handling multiple documents.
All the update requests are backed with HEAD requests to see if content has
changed and on which side (repo or local).
Do take a look at the video and give feedback. I think this is close to a full
SIMPLE implementation of SWORDv2, e.g. without on behalf of and other complex
headers.
The next thing to look into is how to move the object through the workflow.
See people at Dev8D where I can do a live demo.
Dave T
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Sword-app-techadvisorypanel mailing list
Sword-app-techadvisorypanel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sword-app-techadvisorypanel
