#include <dc_buffered_stream_receive.hpp>

Inheritance diagram for graphlab::dc_impl::dc_buffered_stream_receive:

Public Member Functions
	dc_buffered_stream_receive (distributed_control *dc)
void	incoming_data (procid_t src, const char *buf, size_t len)
void	function_call_completed (unsigned char packettype)

Detailed Description

Receiver processor for the dc class. The job of the receiver is to take as input a byte stream (as received from the socket) and cut it up into meaningful chunks. This can be thought of as a receiving end of a multiplexor. This receiver performs buffered receives. That is, the incoming data is placed in a buffer, which is then processed by a parsing thread, before passing off to the actual function call handlers.

This implements a buffered receiver and can be enabled by passing "buffered_recv=yes" in the distributed control initstring.

Note:: this class is not very useful since process_buffer is not usually a significant overhead. Using buffered receives tend to decrease performance in practice

Definition at line 50 of file dc_buffered_stream_receive.hpp.

Member Function Documentation

void graphlab::dc_impl::dc_buffered_stream_receive::function_call_completed ( unsigned char packettype ) [virtual]

called by the controller when a function call is completed

Implements graphlab::dc_impl::dc_receive.

void graphlab::dc_impl::dc_buffered_stream_receive::incoming_data	(	procid_t	src,
		const char *	buf,
		size_t	len
	)			`[virtual]`

Called by the controller when there is data coming from the source

Implements graphlab::dc_impl::dc_receive.

The documentation for this class was generated from the following file:

src/graphlab/rpc/dc_buffered_stream_receive.hpp

graphlab::dc_impl::dc_buffered_stream_receive Class Reference [GraphLab RPC]

Public Member Functions

Detailed Description

Member Function Documentation

graphlab::dc_impl::dc_buffered_stream_receive Class Reference
[GraphLab RPC]