Schema Versions for XLF and XMDS
Implement a schemaVersion for XLF and XMDS.
Store in the version table.
Blueprint information
- Status:
- Complete
- Approver:
- Dan Garner
- Priority:
- Medium
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- Dan Garner
- Definition:
- Approved
- Series goal:
- Accepted for 1.0
- Implementation:
-
Implemented
- Milestone target:
-
1.0.0-rc3
- Started by
- Dan Garner
- Completed by
- Dan Garner
Whiteboard
Added the columns to the version table and altered the Config class to return the new versions.
Will now need to add to the XLF generation routine and to XMDS.. not sure how to add to XMDS, I believe it is just a compare on the version parameter.
Perhaps have a method for checking the version (part of auth?) that will raise a SOAP fault
Alex: XMDS Schema version is passed in on every call. No need for a new call IMO. Plus you'd want the client to stop calling if the server version is incremented while it's running. If it were a single call run once on startup, then the client would keep spamming the server until it was restarted?
I think it's a simple "is equal" comparison on each of the xmds calls. If not equal, raise an error. Client will need to deal with the error in some sane way (like sleeping the xmds threads for 2x normal interval or somesuch).
Dan: Ok so from the servers point of view all that now has to be done will be to compare the request version with the current version of the service. And throw a SOAP error if they are different.
I believe this may be done already, but I will check and mark this blueprint accordingly.
Dan: There is a CheckVersion function in XMDS that is not called and just returns true even if it were called. Therefore I will branch for implementing this version checking in the XMDS. The version parameter is already expected on all calls.
Dan: A SOAP error will be given as a response if the client versions do not match
