Closed GoogleCodeExporter closed 9 years ago
Mike,
I've taken an initial stab at it in r158
Codec tests split out into various files, making it easier to manage the test
suite for any one particular codec.
All decode and encode tests are not stubbed in.
Note - this stuff is basically stubbed so that the codec author fixes up the
tests as they go on. Anything with
TODO is truly TODO. See the J2EE reference implementation to figure out WHAT
the PHP version should be
encoding / decoding. We must be reference compatible so that a J2EE and PHP app
communicating (say over
Ajax or RPC) can encode and decode safely together.
Mike - the stubs are now back in the hands of the codec builders.
Interestingly, 7 tests pass. :-)
Original comment by vande...@gmail.com
on 28 Oct 2009 at 10:28
Original issue reported on code.google.com by
mike.bob...@gmail.com
on 27 Oct 2009 at 4:57