Acting a source of data (legacy API)

Functions
void	deregister_provider (const char *pattern, provider_cb provider_fn)
	Deregisters the data provider with the Transformer core for the specified object name pattern. The data provider will no longer be informed of any requests for objects with names that match the pattern. More...
void	register_provider (const char *pattern, provider_cb provider_fn)
	Registers the specified data provider with the Transformer core for the specified object name pattern. The data provider will be informed of any requests for objects with names that match the pattern. More...

Detailed Description

The old Transformer API is still supported, but we recommend that any new development use the new provider API instead of the legacy equivalents.

Function Documentation

void deregister_provider	(	const char *	pattern,
		provider_cb	provider_fn
	)

Deregisters the data provider with the Transformer core for the specified object name pattern. The data provider will no longer be informed of any requests for objects with names that match the pattern.

Parameters

pattern	The object name pattern the provider can provide.
provider_fn	The callback to call when the specified pattern is requested by a DataSource peer

Deprecated:

The use of filename-style wildcards is being deprecated throughout the Caplin platform in favour of standard regular expressions. The replacement API fully supports regular expressions.

Note

The callbacks generated by registrations of this type on single threaded.

void register_provider	(	const char *	pattern,
		provider_cb	provider_fn
	)

Registers the specified data provider with the Transformer core for the specified object name pattern. The data provider will be informed of any requests for objects with names that match the pattern.

Parameters

pattern	The object name pattern the provider can provide.
provider_fn	The callback to call when the specified pattern is requested by a DataSource peer

Deprecated:

The use of filename-style wildcards is being deprecated throughout the Caplin platform in favour of standard regular expressions. The replacement API fully supports regular expressions.

Note

The callbacks generated by registrations of this type on single threaded.