Re: Standalone xPL Hub Summary, Mark II

["Mal Lansell" <mal@xxxxxxxxxxx>]

I currently only block messages when awaiting configuration (and
there is also a method IsInConfigMode() that allows the application
to check).

With built-in hubs, the application was free to assume that a hub
would be available.  With a stand-alone hub, that will change.

I would block all application messages while awaiting configuration
and while waiting for the hub to appear (assuming that the framework
handles all config and hbeat messages).  Any SendMessage() method
should fail with an appropriate error.

Mal



--- In ukha_xpl@xxxxxxx, Tom Van den Panhuyzen <tomvdp@g...>
wrote:
> While an application is waiting for a hub and it is sending out
hbeats at a
> higher frequency, is it allowed to send out regular xpl-msgs ? I
am asking
> because probably the "framework" (xpllib, ocx,
java-container)
will handle
> the hbeat-stuff and that framework knows the xpl-msg will not be
delivered.
> Hence it can raise the issue to the application.
>
>
> [Non-text portions of this message have been removed]