| Age | Commit message (Collapse) | Author | 
 | 
Implements the SP wire protocol, and infrastructure for legacy wire
protocol support.
Also added an XS_SERVICE_ID socket option to set the service id and renamed
the XS_PROTOCOL option to XS_PATTERN_VERSION.
The following pattern versions are supported:
PAIR:     v3
PUBSUB:   v1 (legacy), v4
REQREP:   v2
PIPELINE: v3
SURVEY:   v2
Note that all existing pattern versions have been bumped by 1 to allow for
use of legacy protocols (otherwise there would be no way to distinguish
between e.g. PUBSUB v3 and PUBSUB v3 using SP).
Signed-off-by: Martin Lucina <martin@lucina.net>
 | 
 | 
This reverts commit 512f3a604924fec9d89e2b4bfd6f73aa66309fa7.
 | 
 | 
Implements SP protocol versioning, legacy protocol support, and the
following pattern protocol versions:
PAIR:     v2
PUBSUB:   v1 (legacy), v3
REQREP:   v1
PIPELINE: v2
SURVEY:   v1
Engine support is only for stream_engine_t at this stage.
Signed-off-by: Martin Lucina <martin@lucina.net>
 | 
 | 
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
 | 
 | 
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
 | 
 | 
The relationship of these two classes was 1:1.
Thus one of them was obsolete.
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
 | 
 | 
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
 | 
 | 
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
 | 
 | 
Older versions of gcc have problems with in-line forward declarations
when there's a naming conflict with a global symbol.
Signed-off-by: AJ Lewis <aj.lewis@quantum.com>
Expand the original patch to all such forward declarations.
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
 | 
 | 
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
 | 
 | 
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
 | 
 | 
This is a preliminary patch allowing for socket-type-specific
functionality in the I/O thread. For example, message format
can be checked asynchronously and misbehaved connections dropped
straight away.
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
 | 
 | 
The engine was not used exclusively for TCP connections.
Rather it was used to handle any socket with SOCK_STREAM
semantics. The class was renamed to reflect its true function.
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
 |