This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision |
| 3500:0400:0410 [2026/08/13 00:55] – ↷ Page moved from docs:3500:0400:0410 to 3500:0400:0410 localdev | 3500:0400:0410 [2026/08/13 02:57] (current) – external edit 127.0.0.1 |
|---|
| If communication with the external party requires that messages be sent from //**AwareIM**// to the external party the specific Sink needs to be implemented (//**AwareIM**// framework will automatically provide the corresponding Source). If communication requires that messages be sent from the external party to //**AwareIM**// the specific Source needs to be implemented (//**AwareIM**// framework will automatically provide the corresponding Sink). | If communication with the external party requires that messages be sent from //**AwareIM**// to the external party the specific Sink needs to be implemented (//**AwareIM**// framework will automatically provide the corresponding Source). If communication requires that messages be sent from the external party to //**AwareIM**// the specific Source needs to be implemented (//**AwareIM**// framework will automatically provide the corresponding Sink). |
| |
| Messages that float between //**AwareIM**// and external party represent arrays of DataObject’s. DataObject is the class that allows defining any number of attributes of different types and provides generic access to them - very much like the [[docs:3500:0300:0317|IEntity]] interface (in fact ''IEntity'' is a wrapper around ''DataObject''). ''DataObject'' exposes the ''[[pr_methods:getattributevalue|getAttributeValue]]'' and ''[[pr_methods:setattributevalue|setAttributeValue]]'' methods that allow access to the values of its attributes. | Messages that float between //**AwareIM**// and external party represent arrays of DataObject’s. DataObject is the class that allows defining any number of attributes of different types and provides generic access to them - very much like the [[3500:0300:0317|IEntity]] interface (in fact ''IEntity'' is a wrapper around ''DataObject''). ''DataObject'' exposes the ''[[ref:p_m:getattributevalue|getAttributeValue]]'' and ''[[ref:p_m:setattributevalue|setAttributeValue]]'' methods that allow access to the values of its attributes. |
| |
| //**AwareIM**// sends ''DataObjects'' of some specific structure to the external party and it expects ''DataObjects'' of this structure from the external party. As explained in the previous section this structure implies that there are only two forms of requests that can be sent between //**AwareIM**// and the external party – service requests and notifications. | //**AwareIM**// sends ''DataObjects'' of some specific structure to the external party and it expects ''DataObjects'' of this structure from the external party. As explained in the previous section this structure implies that there are only two forms of requests that can be sent between //**AwareIM**// and the external party – service requests and notifications. |
| |
| //**AwareIM**// provides two utility classes [[docs:3500:0400:0410:0415|MessageBuilder]] and [[docs:3500:0400:0410:0414|MessageInterpreter]] that allow a programmer to easily create or read messages representing service requests and notifications without knowing too many details about the underlying structures of ''DataObjects'' and its attributes. | //**AwareIM**// provides two utility classes [[3500:0400:0410:0415|MessageBuilder]] and [[3500:0400:0410:0414|MessageInterpreter]] that allow a programmer to easily create or read messages representing service requests and notifications without knowing too many details about the underlying structures of ''DataObjects'' and its attributes. |
| |
| To summarize a programmer has to do the following: | To summarize a programmer has to do the following: |
| The details of this process are described in the sections below. | The details of this process are described in the sections below. |
| |
| {{simplenavi>:docs:3500:0400:0410}} | {{simplenavi>.:0410}} |