Meet

JSON Reference

Meet-Point

This is the central meeting point. Both the Publisher and Subscriber connect to this duct point independently. This duct-point retains a list of active publishers by topic name. It will disconnect any publisher connection that is older than 60 seconds. This is usually the last duct-point in a list of duct-points for a tunnel-segment configuration

No value is required, so use an empty string

Example

"Meet-Point":""

Properties

  • Activation Phase = Top Down

  • Type = Application

  • Stream Interaction = One Off

  • JSON Value Type = inline string (empty)

  • Initiator = No

Meet-Publisher

The publisher is the side that is meeting to provide access to a service resource. This connection will last for 60 seconds before being stale and disconnected by the meet-point duct-point. This will typically result in the publisher reconnecting again.

There is a single inline string value parameter:

  • Shared topic name - is a simple string that contains the text of the shared topic name that both the the publisher and subscriber will use to connect

Example

"Meet-Publisher":"SHARED-TOPIC-NAME-HERE"

Properties

  • Activation Phase = Top Down

  • Type = Step

  • Stream Interaction = One Off

  • JSON Value Type = inline string

  • Initiator = No

Meet-Subscriber

The subscriber is the side that is seeking to access a service resource via the meeting point. If a publisher with the same topic name is waiting they will be connected right away. If there is no waiting publisher, the subscriber will wait up to 5 seconds before abandoning the attempt.

There is a single inline string value parameter:

  • Shared topic name - is a simple string that contains the text of the shared topic name that both the the publisher and subscriber will use to connect

Example

"Meet-Publisher":"SHARED-TOPIC-NAME-HERE"

Properties

  • Activation Phase = Bottom Up

  • Type = Step

  • Stream Interaction = One Off

  • JSON Value Type = inline string

  • Initiator = No