Base interface for details of paged topics TopicType.PAGED_RECORD and TopicType.PAGED_STRING. More...

Inheritance diagram for PushTechnology.ClientInterface.Client.Topics.IPagedTopicDetails:

Additional Inherited Members
Properties inherited from PushTechnology.ClientInterface.Client.Topics.ITopicDetails
TopicDetailsLevel	Level `[get]`
	Returns the level of detail available. More...

TopicType	Type `[get]`
	Returns the topic type. More...

ITopicDetailsSchema	Schema `[get]`
	Returns the topic schema. More...

ITopicDetailsAttributes	Attributes `[get]`
	Returns the topic attributes. More...

Detailed Description

Base interface for details of paged topics TopicType.PAGED_RECORD and TopicType.PAGED_STRING.

A paged topic maintains a variable number of lines of data and allows individual clients to positionally navigate through the lines of data and be notified when the state changes.

Different subtypes exist representing different formats of the lines.

Lines of data may be added, removed or updated at any time. Each client that uses the topic may then have a 'paged' view of the data. A client will indicate the number of lines per page it wishes to have in its view. The client may then request any page of the available data and will be notified when the data changes (specifically the page it currently has selected).

Lines within the data may be unordered or ordered. If ordered then the ordering is enforced by a supplied comparator. When ordered, the addition of multiple lines is treated as multiple single additions and therefore may be less efficient. When data is ordered, the duplicates policy determines how lines that are determined to be equal using the comparator are handled.

Deprecated since 5.9.

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

UCIStack/Client/Topics/IPagedTopicDetails.cs

Additional Inherited Members

Detailed Description