For those of you following code commits, you'll notice a good bit of
activity in the OpenSRF new-json2 branch. We've reached a point where the
new protocol is (testing shows) fully backwards compatible with existing
code. In short, you can install the new-json2 branch over an existing
install (e.g. Evergreen install), restart services, and all will be well.
The main noticable difference will be what you see in srfsh responses:
EXAMPLE:
* LEGACY protocol
------------------------------------------------------------------------
srfsh# request open-ils.cstore
open-ils.cstore.direct.actor.org_unit.retrieve 1
Received Data: /*--S aou--*/[
null,
null,
null,
null,
1,
1,
1,
1,
1,
"PINES",
1,
null,
"PINES",
null,
null,
"t"
]
/*--E aou--*/
* NEW protocol
-----------------------------------------------------------------------------
srfsh# request open-ils.cstore
open-ils.cstore.direct.actor.org_unit.retrieve 1
Received Data: {
"__c":"aou",
"__p":[
1,
1,
1,
1,
1,
"PINES",
1,
null,
"PINES",
null,
null,
"t"
]
}
The new JSON protocol will be merged into OpenSRF trunk in preparation for
OpenSRF 1.0. It won't be merged into STABLE_0_9, just to be clear.
Evergreen 1.4 will require OpenSRF 1.0 because of the new JSON code.
The Evergreen 1.2 branch should work with either OpenSRF STABLE_0_9 or
OpenSRF 1.0
I'll be merging the changes today, unless there is any hollering :)
For the really curious:
svn merge -r1006:1012 svn://svn.open-ils.org/OpenSRF/branches/new-json2 .
svn merge -r1018:1019 svn://svn.open-ils.org/OpenSRF/branches/new-json2 .
svn merge -r1022:1025 svn://svn.open-ils.org/OpenSRF/branches/new-json2 .
svn merge -r1026:1028 svn://svn.open-ils.org/OpenSRF/branches/new-json2 .
svn merge -r1036:1037 svn://svn.open-ils.org/OpenSRF/branches/new-json2 .
svn merge -r1039:1040 svn://svn.open-ils.org/OpenSRF/branches/new-json2 .
-bill
