title: Netty dynamic pipeline configuration
body: <p>This may be a "newb" question but here it goes anyway.  We have a netty server up and running and we want it to support multiple different protocols like straight tcp, http, udp etc..  I am trying to write a class to be more dynamic what handlers/decoders/encoders we add to the pipeline on every request so we only add the layers we need depending on what type of traffic it is.  I've got straight tcp figured out because we are encoding special bytes but I'm having a hard time coming up with a clever way to tell if its HTTP traffic vs straight tcp based off a ChannelBuffer or byte array.</p>
  
  <p>My thoughts have been along the line of reading in some bytes and looking for a string like 'GET' or 'POST', I assume a HTTPRequest would have these items somewhere..  Is what I'm trying to do worth it? Or anyone have any helpful ideas?</p>