'[Protocol-dev] How should we handle streaming servers that don't'

[prev in list] [next in list] [prev in thread] [next in thread] 

List: helix-protocol-dev
Subject: [Protocol-dev] How should we handle streaming servers that don't
From: <ext-jussi.1.puhakka () nokia ! com>
Date: 2008-10-15 19:39:35
Message-ID: B86468F2A3D507459769DD1EDD1F64442B2989 () vaebe109 ! NOE ! Nokia ! com
[Download RAW message or body]

--===============0102173812==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C92EFD.C1478D05"

This is a multi-part message in MIME format.

Hi, I would like to raise discussion about the rtsp and streaming
servers that don't support pause (and are not live content). Such event
can be possible according to rfc, however unlikely(?), but..
So we have encountered couple of these kind servers and would like to
discuss how should we handle this kind of scenario.

Here is one use case:

We could violate the rfc and sending pause every time we are pausing
such a stream, however on servers that doesn't support pause (and I
think helix wont send it to server either anymore if not supported), it
only pauses client side, while server keeps playing (and sending
packets) and sub sequential play command there causes either play
command to be in queue (depending of usage of range parameter) or
resuming to that part / buffer which is currently playing.=20

Also, I would like to ask that why there are these not live servers that
doesn't support pause, are those servers intentionally so or just mishap
in configuration, any ideas?

Thanks,
-Jussi

[Attachment #3 (text/html)]

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7653.3">
<TITLE>How should we handle streaming servers that don&#8217;t support pause?</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<BR>

Hi, I would like to raise discussion \
about the rtsp and streaming servers that don't support pause (and are not live \
content). Such event can be possible according to rfc, however unlikely(?), \
but..

<P><SPAN LANG="fi"><FONT SIZE=2 FACE="Arial">So we have encountered couple of these \
kind servers and would like to discuss how should we handle this kind of \
scenario.</FONT></SPAN></P>

<P><SPAN LANG="fi"><FONT SIZE=2 FACE="Arial">Here is one use case:</FONT></SPAN>
</P>

We could violate the rfc and sending \
pause every time we are pausing such a stream, however on servers that doesn't \
support pause (and I think helix wont send it to server either anymore if not \
supported), it only pauses client side, while server keeps playing (and sending \
packets) and sub sequential play command there causes either play command to be in \
queue (depending of usage of range parameter) or resuming to that part / buffer which \
is currently playing.

<P><SPAN LANG="fi"><FONT SIZE=2 FACE="Arial">Also, I would like to ask that why there \
are these not live servers that doesn't support pause, are those servers \
intentionally so or just mishap in configuration, any ideas?</FONT></SPAN></P>

<P><SPAN LANG="fi"><FONT SIZE=2 FACE="Arial">Thanks,</FONT></SPAN>

<BR><SPAN LANG="fi"><FONT SIZE=2 FACE="Arial">-Jussi</FONT></SPAN>
</P>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>

</BODY>
</HTML>

_______________________________________________
Protocol-dev mailing list
Protocol-dev@helixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/protocol-dev

--===============0102173812==--

[prev in list] [next in list] [prev in thread] [next in thread] 