TCP/IP broadcast handler limitations: Difference between revisions

From Planimate Knowledge Base
Jump to navigation Jump to search
m (1 revision(s))
No edit summary
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<font face="Arial">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...)
----




1. A network/socket broadcast must not<br /> cause a change in the current panel - its meant to be a background<br /> activity.




2. The animation of network broadcasts is not interruptable - if your<br /> model cannot keep up with the incoming broadcast stream<br /> (because you are animating them) then you will be blocked<br /> from stopping the model until you stop the network broadcasts<br /> (stop the sender, pull out a network cable etc...)<br /><font face="MS Sans Serif"><br /> </font></font>
<font size="2">idkbase note 136</font>
----
 
[[Category:Broadcast]]
[[Category:Broadcast]]
[[Category:Event/FEC]]
[[Category:Runtime Engine]]
[[Category:Runtime Engine]]
[[Category:Socket (TCPIP)]]
[[Category:Data/Exchange]]
[[Category:Release Note]]
<font size="2">idkbase note 136</font>

Latest revision as of 03:30, 13 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