Starting with tag: [TAG before-json-rpc-2 Henrik Hjelte **20100117215948 Ignore-this: 6ec3790b4b95f6812d4b8e24946d1ab9 ] [json-rpc-handle-notifications rpgoldman@sift.info**20091230211756 A couple of modifications to hande JSON-RPC notifications (like normal requests, but they don't expect a response). Also made it possible to invoke a helper function of invoke-json with the pieces of the request. This is necessary because you can't use the standard invoke-rpc if you've already parsed the JSON message from the client. ] [removed-allegro-from-some-tests rpgoldman@sift.info**20100102221106 Some tests don't work on allegro on macosx or on allegro simpliciter. These seem like limitations of allegro, so I have added features flags to mask them. ] [catch-read-numeric-overflow-on-allegro rpgoldman@sift.info**20100105201756 On Allegro Common Lisp, when there's a numeric overflow in the reader, they don't signal a reader-error, but a simple-error (I have reported this and they may fix it in the future). This patch makes use of information about that simple-error to catch the case in parse-number and treat it the way parse-number overflows are handled on other lisps. ] [fixed-allegro-reader-error rpgoldman@sift.info**20100110051717] [reorganized-json-rpc-encoding rpgoldman@sift.info**20100110051821 Reorganized JSON-RPC result encoding, using CLOS, to make it more flexible, along lines discussed on the mailing list. Also added /partial/ support for JSON-RPC 2.0. This support is not yet tested in the test suite. ] [export-json-rpc-version-constants rpgoldman@sift.info**20100113210938] [record-function-names-not-functions rpgoldman@sift.info**20100114024541 Originally, when one defined a function to be exported as a json-rpc function, the function object was cached in a hash table. This made it very difficult to debug with the CL tracer, since the trace-encapsulated function wouldn't make it onto the function table. However, this problem goes away with this patch, which caches the function /name/ (a symbol) instead of the function itself. Since json-rpc functions are invoked with APPLY, nothing else need change. Slightly less efficient, but JSON-RPC is never going to be that efficient anyway. ] [add-json-rpc-2.0-support rpgoldman@sift.info**20100114024858 A large number of changes that provide json-rpc-2.0 support to cl-json. Tests are included. ] [Killed some trailing whitespace. rpgoldman@sift.info**20100115234144] [Fix to ENCODE-JSON-NUMBER to remove D characters that break the JSON readers. rpgoldman@sift.info**20110622211339] [Better fix to ENCODE-JSON-NUMBER from Boris Smilga. rpgoldman@sift.info**20110623005733] [Tweak to Boris Smilga's ENCODE-JSON-NUMBER fix. Sort float subtypes from smallest to largest. rpgoldman@sift.info**20110623010610] [Add check for rationals to ENCODE-JSON-NUMBER, per Boris Smilga. rpgoldman@sift.info**20110623144708] [Refactoring of the rational test in ENCODE-JSON-NUMBER, per Boris Smilga. rpgoldman@sift.info**20110624022244] [bump-to-0.4.1 rpgoldman@sift.info**20110625000531] [Fixed typecase in ENCODE-JSON-NUMBER. rpgoldman@sift.info**20110625030416] [Added conditional compilations to kill Clozure etypecase warnings. rpgoldman@sift.info**20110625151607] [Added test case to check for exponent markers in float encodings. rpgoldman@sift.info**20110625151708] [TAG 0.4.1 henrik@evahjelte.com**20110613193019 Ignore-this: 924d35e78a9ff89c8c3c37272cddf8ea ] [Update html page henrik@evahjelte.com**20110613194142 Ignore-this: 9c948326a48610d42bf3bce9e6ab9ed3 ]