Commit | Date | |
---|---|---|
2010-05-06 19:43:28 | Tree | |
2010-05-06 19:42:55 | Tree | |
2010-05-06 17:34:30 | Tree | |
[r1653]
by
briggs@adobe.com
Add to ExamplePlayer a ProxyElement class that forces the urlIncludesFMSApplicationInstance param to be true. Can be useful for plugins for CDNs that require this param (i.e. so that they don't get errors if the client fails to specify it). |
2010-05-06 17:30:58 | Tree |
2010-05-05 21:52:11 | Tree | |
[r1651]
by
weizhang@adobe.com
Add an additional fix to FM-826. The previous fix will continue to search for good fragment until it reaches the end. Therefore, it will take a while to stop and return error message. This may not be desirable if there are hundreds of bad fragments. A better way is to fail fast, i.e. http streaming playback should fail the moment it seems a bad fragment and this is the fix all about. |
2010-05-05 19:10:16 | Tree |
[r1650]
by
briggs@adobe.com
Fix FM-833: RTE when loading VAST document. The problem was that we listened for the event on the loader, but didn't filter out events for other load traits. |
2010-05-05 17:39:27 | Tree |
[r1649]
by
briggs@adobe.com
Fix FM-824: Cannot know currentChild of SerialElement generated by a plugin. Update unit tests to verify. |
2010-05-05 03:23:27 | Tree |
[r1648]
by
weizhang@adobe.com
Fix bug FM-826. Here is a summary: when the data in a fragment is mangled, http streaming starts to encounter bad box type and bad box size, such as 30 billion bytes. For any "unfamiliar" box type, http streaming will skip the box based on the box size. However, there is a flaw in HTTPNetStream that cast the bytes needed to int type. This will generate a negative value for bytes needed, thereby breaking the logic. The fix is simple, change from int type to Number type. The if clause is just a safe guard. |
2010-05-05 01:14:46 | Tree |
2010-05-05 00:37:44 | Tree |