Will Protocol Buffers constrain me to Netty?

[Marc-André Laverdière]

Protocol buffers give you interoperability across platforms and
programming languages.
Let the others use whatever network api they wish... at the end of the
day everyone will speak protobuf.

Marc-André LAVERDIÈRE
"Perseverance must finish its work so that you may be mature and
complete, not lacking anything." -James 1:4
mlaverd.theunixplace.com/blog

 /"\
 \ /    ASCII Ribbon Campaign
  X      against HTML e-mail
 / \



2010/7/3 anthony_w <awwold69 at hotmail.com>:
>
> 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.
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users
>