TCP/IP broadcast handler limitations: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
As with a timed broadcast: | As with a timed broadcast: | ||
1. A network/socket broadcast must not cause a change in the current panel - its meant to be a background activity. | |||
2. The animation of network broadcasts is not interruptable - if your model cannot keep up with the incoming broadcast stream (because you are animating them) then you will be blocked from stopping the model until you stop the network broadcasts (stop the sender, pull out a network cable etc...) | |||
---- | |||
2 | <font size="2">idkbase note 136</font> | ||
[[Category:Broadcast]] | [[Category:Broadcast]] | ||
[[Category:Event | [[Category:Event]] | ||
[[Category:FEC]] | |||
[[Category:Runtime Engine]] | [[Category:Runtime Engine]] | ||
[[Category:Socket (TCPIP)]] | [[Category:Socket (TCPIP)]] | ||
Revision as of 02:54, 12 January 2008
As with a timed broadcast:
1. A network/socket broadcast must not cause a change in the current panel - its meant to be a background activity.
2. The animation of network broadcasts is not interruptable - if your model cannot keep up with the incoming broadcast stream (because you are animating them) then you will be blocked from stopping the model until you stop the network broadcasts (stop the sender, pull out a network cable etc...)
idkbase note 136