Any message could be too large for either the client or server. In most cases, the client will receive a 'limits exceeded' fault if this happens and the client will send its request again with different parameters.

However, this approach will not work for Publish responses where the client has no direct control over the size of the data returned. Two changes could remedy this:

1) The subscription needs a MaxNotificationsPerPublish parameter that allows the client to limit the size of Publish response messages.

2) The Republish should allow clients to request partial messages by specifying an IndexRange along with the MessageId.