Abstract: A system may receive application data in a client-incompatible format and convert at least a portion of the application data into an alternate client-compatible format. In one example, the incompatible format may comprise Enhanced Binary Interchange Format (EBIF) while a client-compatible format may include a web format such as JavaScript, XML or HTML. Interactions (e.g., commands and user input) associated with the application may be received and converted. The interactions may then be processed using the application.

Abstract: Content segments may be generated/sent in a different format than the format they are stored/received. Timing information for packets comprising the content segments in the requested format may be based on timing information for packets comprising the content segment in the stored format. For example, the timing information of the first packet in the requested format may comprise the timing information of the first packet in the stored format. The timing information of other packets in the requested format may be based on the timing information of the first packet in the requested format.

Abstract: Methods and systems for routing voice over internet protocol (VOIP) are described. A service provider may provide a VOIP infrastructure for routing VOIP calls. One or more other service providers may join the VOIP infrastructure. A computing device may identify the service provider servicing the VOIP calls and may further process the calls accordingly.