Gv::RtpServer Class Reference

An RTP server class. More...

#include <gvrtpserver.h>

Inheritance diagram for Gv::RtpServer:

Public Member Functions
	RtpServer (RtpServerHandler &, int scale, bool monochrome, GNet::Address bind_address, const std::string &group_address, unsigned int packet_type, const G::Path &fmtp_file, int jpeg_fudge_factor, const std::string &filter_spec, unsigned int source_stale_timeout)
	Constructor. More...
virtual	~RtpServer ()
	Destructor.
Public Member Functions inherited from GNet::EventHandler
virtual	~EventHandler ()
	Destructor.
virtual void	writeEvent ()
	Called for a write event. More...
virtual void	exceptionEvent ()
	Called for a socket-exception event. More...

Additional Inherited Members
Protected Member Functions inherited from GNet::EventExceptionHandler
virtual	~EventExceptionHandler ()
	Destructor.

Detailed Description

An RTP server class.

Definition at line 52 of file gvrtpserver.h.

Constructor & Destructor Documentation

Gv::RtpServer::RtpServer	(	RtpServerHandler &	handler,
		int	scale,
		bool	monochrome,
		GNet::Address	bind_address,
		const std::string &	group_address,
		unsigned int	packet_type,
		const G::Path &	fmtp_file,
		int	jpeg_fudge_factor,
		const std::string &	filter_spec,
		unsigned int	source_stale_timeout
	)

Constructor.

The received images are delivered to the given callback interface.

If a non-zero packet type is specified it should normally be 26 for "JPEG/90000" or some value in the dynamic range (96..127) for "H264/90000". In principle the sdp attribute "rtpmap" should be used to map from "H264/90000" to the dynamic packet type, but a fixed value of 96 is often adequate. If a zero packet type is specified then the type of the first packet received is used.

Definition at line 37 of file gvrtpserver.cpp.

---

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

• /home/graeme/videotools/src/gvideo/gvrtpserver.h
• /home/graeme/videotools/src/gvideo/gvrtpserver.cpp