[MPlayer-dev-eng] problem in seek bar functionality

Sun Apr 21 14:17:46 CEST 2002

hi,
   i hacked Windows Media Player Commands through
proxy server, and got information about how HTTP on
MMS Server works.

1. 	When i send the first request to the server

GET /baby_256.asf HTTP/1.0
Accept: */*
User-Agent: NSPlayer/4.1.0.3856
Host: 192.168.0.169:80
Pragma:
no-cache,rate=1.000000,stream-time=0,stream-offset=0:0,request-context=1,max-duration=0
Pragma:
xClientGUID={c77e7400-738a-11d2-9add-0020af0a3278}

2. 	This is the response i get from the server

HTTP/1.0 200 OK
Content-Type: application/octet-stream
Server: Cougar 4.1.0.3917
Cache-Control: no-cache
Pragma: no-cache
Pragma: client-id=25
Pragma: features="seekable,stridable"

3.	Before actually playing its sends request with
stream time and offset.Here stream-time=0 ,which means
it will start from the begining.I get the
stream-offset constant value everytime.i dont know
why??

GET http://192.168.0.169/baby_256.asf HTTP/1.0
Accept: */*
User-Agent: NSPlayer/7.1.0.3055
Host: 192.168.0.169
Pragma:
no-cache,rate=1.000000,stream-time=0,stream-offset=4294967295:4294967295,request-context=107916544,max-duration=0
Pragma: xPlayStrm=1
Pragma:
xClientGUID={A1FC2274-3E3D-4A74-9EF8-11FC45D95517}
Pragma: stream-switch-count=2
Pragma: stream-switch-entry=ffff:1:0 ffff:2:0

4.	this is the response i get from the Server.Here
client-id tells my id at the server side.

HTTP/1.0 200 OK
Content-Type: application/octet-stream
Server: Cougar 4.1.0.3917
Cache-Control: no-cache
Pragma: no-cache
Pragma: client-id=35
Pragma: features="seekable,stridable"

5.	This is the response i get when i use the
forward/reverse buttons.So this the response i get
from the server after pressing the forward
button(client-id remains the same).

POST http://192.168.0.169/baby_256.asf HTTP/1.0
Accept: */*
User-Agent: NSPlayer/7.1.0.3055
Pragma: client-id=35
Pragma: log-line=192.168.0.169 2002-04-18 22:47:46 -
http://192.168.0.169/baby_256.asf 0 9 1 -
{A1FC2274-3E3D-4A74-9EF8-11FC45D95517} 7.1.0.3055
en-US - - wmplayer.exe 7.0.0.1954 Windows_2000
5.0.0.2195 Pentium 238 7608651 233103 http TCP
Windows_Media_Audio_V2 Microsoft_MPEG-4_Video_Codec_V3
- - 396276 - 135 0 0 0 0 0 0 1 5 100 - - - -
Content-Length: 0
Pragma:
xClientGUID={A1FC2274-3E3D-4A74-9EF8-11FC45D95517}

6.	After the above POST request,it sends the below GET
request with stream-time= ?? milisecs.I tried to find
why it first sends a POST first and then a GET
requset,but could not get it.

GET http://192.168.0.169/baby_256.asf HTTP/1.0
Accept: */*
User-Agent: NSPlayer/7.1.0.3055
Host: 192.168.0.169
Pragma:
no-cache,rate=1.000000,stream-time=202389,stream-offset=4294967295:4294967295,request-context=107914912,max-duration=0
Pragma: xPlayStrm=1
Pragma:
xClientGUID={A1FC2274-3E3D-4A74-9EF8-11FC45D95517}
Pragma: stream-switch-count=2
Pragma: stream-switch-entry=ffff:1:0 ffff:2:0

7.	This is the response from the server,with a
DIFFERENT client-id.	

HTTP/1.0 200 OK
Content-Type: application/octet-stream
Server: Cougar 4.1.0.3917
Cache-Control: no-cache
Pragma: no-cache
Pragma: client-id=38
Pragma: features="seekable,stridable"

8.	When the movie is stopped by the user,this is what
i get.

POST http://192.168.0.169/baby_256.asf HTTP/1.0
Accept: */*
User-Agent: NSPlayer/7.1.0.3055
Pragma: client-id=38
Pragma: log-line=192.168.0.169 2002-04-18 22:47:53 -
http://192.168.0.169/baby_256.asf 6 0 1 -
{A1FC2274-3E3D-4A74-9EF8-11FC45D95517} 7.1.0.3055
en-US - - wmplayer.exe 7.0.0.1954 Windows_2000
5.0.0.2195 Pentium 238 7608651 265489 http TCP
Windows_Media_Audio_V2 Microsoft_MPEG-4_Video_Codec_V3
- - 9624 - 3 0 0 0 0 0 0 1 0 100 - - - -
Content-Length: 0

This is my study of what the Windows Media
Administrator(MMS server) Publishing Point Clients.

In the Windows Media Administrator,
client-id 	client-ipaddress	clientport	status	
filename
   35		   192.168.0.1		   5300		streaming	
c:\asfroot\baby_256.asf     	

(After i press the FORWARD button)
   38		   192.168.0.1		   5302		streaming	
c:\asfroot\baby_256.asf

This is my study of how Windows Media Player interacts
with the MMS server through HTTP .
But i have some doubts regarding the all the data i
supplied above 

1st)When the FORWARD/REVERSE button is pressed
,windows media player closes the current connection
and creates a fresh connection.I doubt that the POST
request( i have given as No. 5 & No. 8) is used to
close the connection.So he is getting all the headers
again ,and i have no way restart that movie again
according to the new connection parameters??

2nd) How do i flush the cache and rebuffer it again??
.

With my limited knowledge i have written some code(but
its incomplete).If u want i can post that code(i didnt
post it here becoes this mail is already quiet long
:).

can u give me any idea of how to go about solving this
problems i mentioned above.

any help will be highly appreciated.
thanking u in advance.

abhijeet

__________________________________________________
Do You Yahoo!?
Yahoo! Games - play chess, backgammon, pool and more
http://games.yahoo.com/