The Replay.json protocol commands currently mention serialization but these methods aren't actually used to serialize/deserialize recordings. (In a future patch I plan to implement serialization/deserialization, which will hand a big JSON string to the backend and get a session or segment back, or vice-versa. The frontend may or may not be involved in that, but in any case, these names are misleading)
<rdar://problem/17920272>
Created attachment 236044 [details] Patch
Committed r172080: <http://trac.webkit.org/changeset/172080>