Release 277
16 December, 2010 - 23:14
iServer bug fixes only - if you arent' using this component its not necessary to update.
- On high traffic networks or if an application generates a quick burst of multiple messages these could be bunded into the same TCP packet. As each message was being 0x00 byte terminated the flash application would only process the 1st message resulting in subsequent messages being ignored.
- A non xapFlash application using the iServer was presenting the <xap> tag in mixed case. The iServer protocol, with regards to the <xap> tag, is now case agnostic.