• Post Reply Bookmark Topic Watch Topic
  • New Topic

Netty - custom protocols: decoder vs/and parsers  RSS feed

 
darren hartford
Greenhorn
Posts: 25
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi everyone,
Does anyone have guidelines for custom payloads over TCP, when should you handle a decoder (and to what detail/level), versus when you pass the accumulated information downstream to a parser instead of trying to put it all in a decoder?

For example, when you have something simple that is fixed-width and 10 fields, it's easy to just have the decoder and breakup the 10 fields directly to pass to a processor later.

But getting into variable fields, X12/EDI, delimited formats....what is a good guideline around using Netty's decoder at the TCP receiving level versus getting the start/stop of a payload and then passing the payload to something else (CSV parser, Smooks EDI parser, a separate custom parser)?

thanks!
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!