The September product release is out! Here are the highlights:
- By request, IceLink now has DNS resolution. You can use a host name for the server address and it will be resolved to an IP address automatically (related feature request). Using a hard-coded IP address is of course still OK.
- WebRTC data-channel support has been added! The new DataChannelStream class can be used to create a stream definition that allows text data to be passed between Chrome and .NET/Java/iOS/Mac/Android/etc. Web browser support is currently limited to Chrome, but will be expanded to include Firefox once SCTP integration is finalized in both Chrome and our own implementation for thick clients. Binary support is coming as soon as it is supported in Chrome.
- WebRTC codec registration no longer requires a payload type. We've made several improvements like this to the public API to make things more intuitive and reduce the learning curve as much as possible.
- IceLink servers have a new event API that makes parsing and responding to various request types a much simpler task.
- A bug has been fixed in IceLink that caused audio and/or video to freeze randomly. A glitch in the roll-over counter caused decryption to fail on the receiving end.
- A periodic memory leak in the IceLink server implementations has been sealed.
As always, we welcome your feedback! Check out support.frozenmountain.com to submit and vote on feature requests/ideas as well as ask questions from our technical staff and receive prompt answers. For any other issues, feel free to send us a message.