default io implementation makes mmsx painful
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libmms |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
hi,
this can't really be classified as a bug, but i will try to argue for my patch :)
the mmsx wrapper provides a very convenient interface for applications. however, i have found one issue with it that makes it pretty much useless. this wrapper is a 'try mms, if failed, try mmsh' strategy. i'm proposing changing this to a 'try mmsh, if that fails try mms'. a lot of servers running mmsh streams, seems to use a long time (minutes) to refuse a mms-over-tcp connect attempt. since the default io implementation is sync, this makes for pain in user application.
my patch is based on the observation from some 10-20 streams (mainly mmsh, but also a few some mms-over-tcp). it seems the mms-over-tcp servers immediately refuse mmsh connect attempts. in addition mmsh seems to be the norm these days.
for now i have hacked the client app i''m working on (xbmc).
please consider this for inclusion. feel free to refuse and call me an idiot if there's something i'm missing :)
cheers,
spiff
thanks a lot rambler. ru:80/keksfm? WMContentBitrat e=150000
very useful patch
with it xbmc is opening problem mms streams as this mms://stream03.
in 2-3 seconds