|
|||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |
See:
Description
Interface Summary | |
---|---|
Configuration | Configuration with settings associated with one network buffer. |
Configuration.NetworkFilter | Filter applied on incoming KNX messages from the KNX network. |
Configuration.RequestFilter | Filter applied on requests to the network buffer from users or components working with the network buffer. |
LDataObjectQueue.QueueListener | Listener for queue events. |
Class Summary | |
---|---|
CommandFilter | Predefined filter for filtering KNX messages of command based datapoints into the associated network buffer configuration and handling requests for this kind of messages. |
LDataObject | Used for holding CEMILData frames. |
LDataObjectQueue | A CacheObject used for holding a list of CEMILData frames. |
LDataObjectQueue.QueueItem | Represents an item in the queue, holding one L-Data frame and its timestamp. |
NetworkBuffer | A network buffer temporarily stores KNX network messages. |
StateFilter | Predefined filter for filtering KNX messages of datapoints with state semantic into the associated network buffer configuration. |
Support for temporary storage of KNX network messages.
This is done by using a network buffer with one or more configurations added to it.
This allows to build up and maintain a local process image to answer user queries.
Benefits might be a decreased network load and smaller response time.
Using a network buffer allows polled mode of communication, since handling of
incoming messages can be delayed to some later point in time.
A configuration determines what messages to keep and what messages to
ignore by the use of filters. These filters might be user defined implementations
set for that particular configuration.
Two predefined filters are available to allow state based and command based
network buffering.
|
|||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |