Chris Barber

Would it make sense to be able to configure base64 as a serializer for the REST bridge? This seems like it would be handy because unless I am missing something,...

I have tested out @rsprouse's solution and have found that it behaves quite intuitively imho (and perhaps better than partial overlap would) for selecting a range of a time-series using...

Thoughts?

For anyone wondering about this, txpool is [using](https://github.com/escattone/txpool/blob/master/txpool/pool.py#L481) Twisted's [NetstringReceiver](https://twistedmatrix.com/documents/current/api/twisted.protocols.basic.NetstringReceiver.html) for communicating pickled objects. NetstringReceiver defines [`MAX_LENGTH`](https://twistedmatrix.com/documents/current/api/twisted.protocols.basic.NetstringReceiver.html#MAX_LENGTH) which defaults to [99999](https://github.com/twisted/twisted/blob/e38cc25a67747899c6984d6ebaa8d3d134799415/src/twisted/protocols/basic.py#L120). Setting `MAX_LENGTH` to something larger in txpool's `WorkerProtocol` should...

#3

I observe the same issue on 5.5.3

> thanks for confirming! Looking more into my case, I found that switching to pickle for serialization completely solved the issue. Json recursively expands because it cannot handle the object...

Seems nice. The persistent option is not usable without some way to keep the DB from growing.

A simple workaround is to use pickle for serialization, which won’t inflate the message size.