Because we are doing some research and something pretty complex with tcp
flow control and all we need is the parser to accomplish this. We looked
at both netty and grizzly and would have to make major modifications. Most
people writing parsers write a re-usable one, but we looked at netty's and
their parser is tightly coupled with netty itself. We are hoping grizzly
might have a few classes for parsing that are used that are not so tightly
coupled??? Maybe you could point me to the classes used for parsing?
thanks,
Dean
On Tue, Dec 11, 2012 at 4:49 PM, Ryan Lubke <ryan.lubke_at_oracle.com> wrote:
> already does this - why not use it? Can you go into details on what
> you're trying to accomplish? Also, what version of Grizzly are you
> currently using?