stomp 0.3.3

A full STOMP 1.2 client implementation. Allows programs to interact with message queueing services like ActiveMQ and RabbitMQ.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38

use frame::Frame;

enum ClientFrame {
  Connect(Frame),
  Send(Frame),
  Subscribe(Frame),
  Unsubscribe(Frame),
  Begin(Frame),
  Commit(Frame),
  Abort(Frame),
  Ack(Frame),
  Nack(Frame),
  Disconnect(Frame),
}

/*

TODO methods for each client frame type.

Our client will never have to read these off the wire,
so we can simply offer methods to construct each type
of frame. The methods should require all of the required
Stomp headers as arguments.

Elsewhere (on a StompSession type?), there will be methods
that use the above methods to construct each frame before
actually writing them to the TCP connection.

It might be possible to get away with not creating any 
separate types for ClientFrames. The user will only 
call methods that create short-lived structures behind
the scenes. ServerFrames, however, will require lots
of type safety.
*/

impl ClientFrame {
  
}