Closed danburkert closed 9 years ago
By keeping it as raw bytes it allows the client to specify the serialization format (e.g. capnproto). I would recommend writing a wrapper struct around the client if you want auto serialization through rustc encodable, but by making the lowest level API require it you limit flexibility for all clients.
That's a good point. Let's leave it [u8]
then.
I'm moving
append()
back to acceptingT
s. Behind the scenes we'llbincode
them. This is reasonable because we need to usebincode
(or some other serialization format) to transmit things likeSocketAddr
s in the case of a redirect. I don't really see a need for exposing raw[u8]
at this time.