Producer::send can't send Vec<u8> or [u8] about pulsar-rs

[stearnsc]

I'm totally fine adding ?Sized to the signature as a fix to get it working now (that will also fix the str impl). Adding an impl for Vec<u8> also doesn't bother me, although I was thinking the slice impl would cover that use case.

Long term, I don't feel like I've fully thought through the implications of the Serialize/DeserializeMessage traits as the basis for handling this problem. Given the way the proto works, we need to have owned data in the payload, but most instance of serialization (thinking serde here) will involve copying data at some point, so for those, taking by ref seems to make the most sense. However, that makes it impossible to just pass in an owned Vec without falling back to send_raw.

Alternatively, we could change SerializeMessage::serialize_message to take Self by value, change the signature of send and send_all to take T: SerializeMessage by value, and then impl SerializeMessage for borrowed types in cases where it makes sense (&Foo instead of Foo). My immediate instinct is that that approach feels like an improvement, but I don't feel like I've thought it through enough.

[leshow]

I fiddled around with it earlier today when I originally came across this problem and made Self by value. It works fine, the only problem there is that you may only have a reference to your data, in which case you'll have to clone it at the call site.

I think there could be a third solution, maybe Message holds onto a reference and has a lifetime, like:

struct Message<'a> {
   payload: &'a [u8],
...
}

then,

impl<'a> SerializeMessage for &'a [u8] {
   fn serialize_message(payload: Self) -> Message {
      Message { payload, ..Default::default()
   }
}

I haven't actually tried this though, but something to think about. It could even be something like:

struct Message<'a, B> {  // I believe B: 'a is elided now since 2018
   payload: &'a B,
...
}

Then bound <B: AsRef<[u8]>> in it's impl's.

[stearnsc]

Unfortunately Message has to be 'static because it's immediately sent by channel to the async runtime to be handled.

the only problem there is that you may only have a reference to your data, in which case you'll have to clone it at the call site.

This works if you impl SerializeMessage for a borrow of your struct, something like

#[derive(Debug, Clone, Serialize)]
pub struct Foo {
    pub a: String,
    pub b: u64,
}

impl SerializeMessage for &Foo {
    fn serialize_message(input: &Foo) -> Result<producer::Message, Error> {
        let payload = serde_json::to_vec(input).map_err(..)?;
        Ok(producer::Message { payload, ..producer::Message::default() })
    }
}

then you should be able to still call producer.send(..) with your &Foo

[stearnsc]

Fixed in #61 (at least until we make SerializeMessage work by value instead of by ref)