THRIFT-388. Create a "ONEWAY" message type that is an alias for "CALL"
Pave the way for a new message type for oneway function calls.
For now, just define the constant in all languages and make
server implementations treat it the same way as a normal call.
Only C++ and Erlang currently check the message type (on the
server side).
There is a little bit of redundancy in the Erlang code, but
the alternative is a bit gross, and this split-up will be
necessary eventually when we start handling one-way calls
differently.
git-svn-id: https://svn.apache.org/repos/asf/incubator/thrift/trunk@761389 13f79535-47bb-0310-9956-ffa450edef68
diff --git a/lib/hs/src/Thrift.hs b/lib/hs/src/Thrift.hs
index b3ce8a4..293edf1 100644
--- a/lib/hs/src/Thrift.hs
+++ b/lib/hs/src/Thrift.hs
@@ -118,6 +118,7 @@
data Message_type = M_CALL
| M_REPLY
| M_EXCEPTION
+ | M_ONEWAY
| M_UNKNOWN
deriving Eq
instance Enum Message_type where
@@ -126,12 +127,14 @@
M_CALL -> 1
M_REPLY -> 2
M_EXCEPTION -> 3
+ M_ONEWAY -> 4
M_UNKNOWN -> -1
toEnum t = case t of
1 -> M_CALL
2 -> M_REPLY
3 -> M_EXCEPTION
+ 4 -> M_ONEWAY
_ -> M_UNKNOWN