Will Protocol Buffers constrain me to Netty?

[anthony_w]

I've written a server application in Netty utilizing Google Protoc
Buffers/ProtobufDecoder.  For reason I won't go into, I believe the
developer who is going to write the client piece will probably not embrace
Netty for implementing that.  Am I limiting my options for non-Netty
frameworks or api's for developing a client piece by using protocol buffers? 
I know this isn't directly a Netty question but I thought it might be likely
that someone using Netty and protocol buffers may have already ran into this
scenario.

My fallback plan right now would be to change my implementation to something
like accepting an array of bytes representing a JSON object and then
deserializing that into my protobuf message object.  But that seems like
it's just adding one additional step for no real benefit.
-- 
View this message in context: http://netty-forums-and-mailing-lists.685743.n2.nabble.com/Will-Protocol-Buffers-constrain-me-to-Netty-tp5249156p5249156.html
Sent from the Netty User Group mailing list archive at Nabble.com.