Add message field to quote model

[dbrgn]

The message needs to be embedded, since the webclient might not have received that message yet.

[lgrahl]

Also, have you checked for side effects? This model is being used throughout a couple of other messages and I'm not sure it makes a lot of sense in all of them.

[dbrgn]

Also, have you checked for side effects? This model is being used throughout a couple of other messages and I'm not sure it makes a lot of sense in all of them.

What type of side effects would you expect? All new fields are optional, so the protocol change itself will not break anything, unless it's explicitly handled.

You're right though that creating a quote and retrieving a quote could use separate types (Quote and NewQuote, since when creating a quote the remote client would not send along the message, only the message ID). The downside of a separate type would be that we lose backwards compatibility (since the NewQuote type would probably not include the quoted text).

[dbrgn]

@lgrahl I added some additional notes regarding validation.