You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PANE should use protobufs as the primary means of interaction. On the client side of the protobufs, we will have, for example, 1) Chen's Java API and 2) a telnet/ascii-based interaction server, running the current/traditional PANE protocol. this will be uber-helpful for extending PANE in the future, and for providing a more natural interface to non-interactive clients.
or Thrift? http://thrift.apache.org/ ... http://hackage.haskell.org/package/thrift ... it provides the RPC piece as well as serialization, but unfortunately, the Haskell package is from 2011, whereas Haskell ProtoBufs is from 2012. not sure if that's an issue or a red herring.
PANE should use protobufs as the primary means of interaction. On the client side of the protobufs, we will have, for example, 1) Chen's Java API and 2) a telnet/ascii-based interaction server, running the current/traditional PANE protocol. this will be uber-helpful for extending PANE in the future, and for providing a more natural interface to non-interactive clients.
protobufs for Haskell: http://hackage.haskell.org/package/protocol-buffers
official protobufs site: https://code.google.com/p/protobuf/
The text was updated successfully, but these errors were encountered: