TCP/IP broadcast handler limitations: Difference between revisions
Jump to navigation
Jump to search
m (1 revision(s)) |
No edit summary |
||
| Line 1: | Line 1: | ||
As with a timed broadcast: | |||
| Line 5: | Line 5: | ||
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...) | 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...) | ||
---- | ---- | ||
[[Category:Broadcast]] | [[Category:Broadcast]] | ||
| Line 11: | Line 11: | ||
[[Category:Runtime Engine]] | [[Category:Runtime Engine]] | ||
[[Category:Socket (TCPIP)]] | [[Category:Socket (TCPIP)]] | ||
<font size="2">idkbase note 136</font> | <font size="2">idkbase note 136</font> | ||
Revision as of 17:14, 10 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