Deprecated: Sending Nodata Messages

Functions
void	ds_send_nodata (const char *subject, unsigned short flags)
	Send a "no data" message to all connected DataSource peers. More...
void	ds_send_nodata_direct (const char *subject, unsigned short flags)
	Send a "no data" message to all connected DataSource peers. More...
void	ds_send_nodata_to_peer (int peer, const char *subject, unsigned short flags)
	Send a "no data" message to a specific DataSource pper. More...

Detailed Description

These functions allow a DataSource to inform its peers that an object does not exist. This can be in response to an active request, in which case an F_NOTFOUND flag is typically sent. It could be in response to some external event where the object should be deleted, an F_DELETEOBJECT flag might then be sent to the peers to instruct that the object should be deleted.

Function Documentation

void ds_send_nodata	(	const char *	subject,
		unsigned short	flags
	)

Send a "no data" message to all connected DataSource peers.

Parameters

subject	The name of the object
flags	The type of "no data" message to send

This function is used for signalling that an object is not found

void ds_send_nodata_direct	(	const char *	subject,
		unsigned short	flags
	)

Send a "no data" message to all connected DataSource peers.

Parameters

subject	The name of the object
flags	The type of "no data" message to send

Note

This function will send the message directly, bypassing the active cache

This function is used for signalling that an object is not found

void ds_send_nodata_to_peer	(	int	peer,
		const char *	subject,
		unsigned short	flags
	)

Send a "no data" message to a specific DataSource pper.

Parameters

peer	The DataSource peer to send the message to
subject	The name of the object
flags	The type of "no data" message to send

This function is used for signalling that an object is not found

Note

The peer number is not the DataSource ID specified by datasrc_id parameter in the configuration file, but corresponds to the order of the peer's add-peer entries in the configuration file. The first add-peer is for peer 0, the next peer 1 and so on.

For the purpose of easy integration with the active cache, sending to peer -1 is the equivalent of calling ds_send_nodata().