#header-inner {background-position: right !important; width: 100% !important;}


Interface Points and the Internet.

Stitie Spaces or their parts can be connected with each other via so called 'Interface Points'.

If done via the Internet, TCP or UDP protocols are used, properly as neccessary. But there can be in-single-space, in-memory or other, for example LAN implementations.

In the Internet.

Interface Point takes a Sunsail to be connected with other Stitie Space's Sunsail, and destination's IP address and port as parameters. It can be one-directional or two-directional.

Before accepting a LightPoint, State or Strategy change, an 'Interface Point' can check security certificates' set and process transmitted data and/or code, transforming them if neccessary.

Interface Point accepts data and changes Stitie Space it's connected to when receiving data, by modifying proper Sunsail. It can also send data to other Stitie Space's Interface Point which acts similar way.

Interface point reacts to Sunsail's events, such as afterStateChange(), to send data to other Stitie Space's Interface Point and Sunsail. Or can be contacted directly to send data and/or code. It uses queue buffer to not block Sunsail it's connected to, and can inform about overflows when queried, if possible.

There should be option to send request to execute transmitted code, perhaps together with data in destination Stitie Space.

There should be 'Teleporting Router' implementation which allows for routing 'Command Chain' via multiple 'Stitie Spaces' and internet nodes that are part of such, along unambiguously and precisely defined path.

No comments:

Post a Comment