use inbound/outbound handlers in a few more places
authorJames Sedgwick <jsedgwick@fb.com>
Thu, 30 Apr 2015 01:20:45 +0000 (18:20 -0700)
committerPraveen Kumar Ramakrishnan <praveenr@fb.com>
Tue, 12 May 2015 00:01:18 +0000 (17:01 -0700)
commitfdd8e84bddefb7fbf07df87b9ed83d6b748c68f3
tree618173b0aace12f12177e76dfd5efdaede16842d
parent555213ca924f9e5a174cc8efd0f5da8b6c2ad4a9
use inbound/outbound handlers in a few more places

Summary: Also, instead of throwing on finalize() if there's no inbound/outbound handler in the pipeline, log a warning and throw when the operations are attempted. This was necessary for CodecTest which doesn't use outbound handlers.

Test Plan: unit

Reviewed By: davejwatson@fb.com

Subscribers: trunkagent, fugalh, folly-diffs@, jsedgwick, yfeldblum, chalfant

FB internal diff: D2028176

Tasks: 6836580

Signature: t1:2028176:1430346333:fdd645a535e8158d780cfd1119e27803995b663f
folly/wangle/bootstrap/ServerBootstrap-inl.h
folly/wangle/channel/Handler.h
folly/wangle/channel/Pipeline.h
folly/wangle/channel/test/PipelineTest.cpp
folly/wangle/codec/ByteToMessageCodec.cpp
folly/wangle/codec/ByteToMessageCodec.h
folly/wangle/codec/CodecTest.cpp
folly/wangle/service/ClientDispatcher.h