1,066
社区成员
发帖
与我相关
我的任务
分享
...全文
请发表友善的回复…
发表回复
kmzs 2003-12-10
- 打赏
- 举报
就是点对点的传输（不经过服务器），即使通讯工具也是这样的
lirun 2003-12-10
- 打赏
- 举报
UP
taomaintao 2003-12-10
- 打赏
- 举报
这很简单,隐函着IIS站点嘛!
andysl 2003-12-10
- 打赏
- 举报
谢谢5653325(等待开刃的刀)给我的参考内容!我看-看:)
踏平扶桑 2003-12-10
- 打赏
- 举报
用组播可以实现
组播就是用来1对多进行播放的。
具体的你可以看计算机网络中关于组播的介绍和实现方法，或者看下面的地址
http://www1.baidu.com/baidu?tn=baidu&ct=0&ie=gb2312&bs=rm%B5%C4tag&sr=&z=&cl=3&f=8&word=%D7%E9%B2%A5%B5%C4%D4%AD%C0%ED
组播就是用来1对多进行播放的。
具体的你可以看计算机网络中关于组播的介绍和实现方法，或者看下面的地址
http://www1.baidu.com/baidu?tn=baidu&ct=0&ie=gb2312&bs=rm%B5%C4tag&sr=&z=&cl=3&f=8&word=%D7%E9%B2%A5%B5%C4%D4%AD%C0%ED
andysl 2003-12-10
- 打赏
- 举报
美萍的好像不用啊。
suonety 2003-09-21
- 打赏
- 举报
流媒体服务器对硬件要求相当高，尤其是内存，一般都是用的专业的服务器，至于客户端的数量就要看你的流媒体文件的码流和带宽了
看你的具体需求是点播还是组播
看你的具体需求是点播还是组播
suonety 2003-09-21
- 打赏
- 举报
微软的mms和Real的Rstp都是流式传输协议
suonety 2003-09-21
- 打赏
- 举报
用流媒体格式，比如rm,rmvb,asf等流式媒体格式，比较成功的解决方案有微软的Windows Mdeia System 和REAL 的Real NetWork以及苹果公司的 QuickTime
基本上可以分为编码端（服务器）和解码端（客户端），底层开发的话可以去他们官方网站上下载SDK
再推荐一个关于流媒体技术网站http://www.liumeiti.com (流媒体中国)
Mdeia System http://www.microsoft.com/windows/windowsmedia/default.aspx
Real http://www.real.com
QuickTime http://www.apple.com/quicktime
基本上可以分为编码端（服务器）和解码端（客户端），底层开发的话可以去他们官方网站上下载SDK
再推荐一个关于流媒体技术网站http://www.liumeiti.com (流媒体中国)
Mdeia System http://www.microsoft.com/windows/windowsmedia/default.aspx
Real http://www.real.com
QuickTime http://www.apple.com/quicktime
andysl 2003-09-21
- 打赏
- 举报
可如果有N个客户端请求影音文件，都用Winsock控件发送文件，服务端不是很忙吗？系统资源很容易不够啊。
Donc 2003-09-20
- 打赏
- 举报
E文差看不懂倒~~~
schq 2003-09-20
- 打赏
- 举报
楼上写了些什么？
看不懂
看不懂
planetike 2003-09-18
- 打赏
- 举报
Buffered streams
On-Demand application are generally pull implementations.
· Standard Pull Model (exists in previous version of the driver) - Driver asks for data when it is needed. When no data is available, the drivers just wait until the application gives a new buffer.
In the case of buffered streams, the user is responsible for providing valid data.
Use the open command (FMP_OPEN with the flag FMPF_BUFFERS, pg.Error! Bookmark not defined.) to open a buffered stream.
If a callback function is installed for the driver, it will be called with the FMPF_BUF_CREATE message with the parameter you gave with FMP_OPEN. (If no callback function is defined for the stream initially, then FMPF_BUF_CREATE message will be sent once the callback function is installed .)
A buffered stream will use a buffer in user’s application. No copy of buffer data will be made, so user should be careful not to overwrite data not yet read from the buffer. A buffer is a segment of linear memory anywhere in the physical memory space. You give the driver the address, the size, the mode of access of your buffer, by using FMP_SET command. You can use the FMP_GET command to get status as to how many bytes are left (or have not been read) in the buffer. The driver uses a message (see callback function) to tell the user when all of his buffer has been read (FMPM_BUF_EMPTY). At this time, you can use the FMP_SET command to give new buffer parameters to the driver. If the user decides to ignore the callback message, the buffer will be read again from the start if the flag FMPF_BUF_LOOP is set in FMPI_BUF_MODE.
You can specify a position that will generate a FMPM_BUF_POS message. This can be used to implement a FIFO or to begin preparing data for a ping pong buffer. For example, your buffer has a size of 10kb. You can tell the driver to signal when there are less than 1kb left in the buffer ( pos=1024 ). The message FMPM_BUF_POS will be issued when the position is r7eached. (see Callback functions).
If you write a zero value for the size, the driver will assume the stream has ended and will then set the size of the stream.
The callback function can receive the message FMPM_BUF_SEEK indicating that your next packet of data will have to start at the given offset (specified in bytes) within your stream file.
You don't need to pre-fill your buffers, because at the beginning, the FMPM_BUF_POS message (when you normally prepare the next buffer) will be sent before the FMPM_BUF_EMPTY (where you give a prepared buffer).
With the messages defined, you can manage your buffers inside the callback function, without external initialization or destruction or pre-fill.
Moreover, streams have a user information field FMPI_STM_USER that you can use to store information about the streams buffers, so you can use this and a single callback function for all your streams.
On-Demand application are generally pull implementations.
· Standard Pull Model (exists in previous version of the driver) - Driver asks for data when it is needed. When no data is available, the drivers just wait until the application gives a new buffer.
In the case of buffered streams, the user is responsible for providing valid data.
Use the open command (FMP_OPEN with the flag FMPF_BUFFERS, pg.Error! Bookmark not defined.) to open a buffered stream.
If a callback function is installed for the driver, it will be called with the FMPF_BUF_CREATE message with the parameter you gave with FMP_OPEN. (If no callback function is defined for the stream initially, then FMPF_BUF_CREATE message will be sent once the callback function is installed .)
A buffered stream will use a buffer in user’s application. No copy of buffer data will be made, so user should be careful not to overwrite data not yet read from the buffer. A buffer is a segment of linear memory anywhere in the physical memory space. You give the driver the address, the size, the mode of access of your buffer, by using FMP_SET command. You can use the FMP_GET command to get status as to how many bytes are left (or have not been read) in the buffer. The driver uses a message (see callback function) to tell the user when all of his buffer has been read (FMPM_BUF_EMPTY). At this time, you can use the FMP_SET command to give new buffer parameters to the driver. If the user decides to ignore the callback message, the buffer will be read again from the start if the flag FMPF_BUF_LOOP is set in FMPI_BUF_MODE.
You can specify a position that will generate a FMPM_BUF_POS message. This can be used to implement a FIFO or to begin preparing data for a ping pong buffer. For example, your buffer has a size of 10kb. You can tell the driver to signal when there are less than 1kb left in the buffer ( pos=1024 ). The message FMPM_BUF_POS will be issued when the position is r7eached. (see Callback functions).
If you write a zero value for the size, the driver will assume the stream has ended and will then set the size of the stream.
The callback function can receive the message FMPM_BUF_SEEK indicating that your next packet of data will have to start at the given offset (specified in bytes) within your stream file.
You don't need to pre-fill your buffers, because at the beginning, the FMPM_BUF_POS message (when you normally prepare the next buffer) will be sent before the FMPM_BUF_EMPTY (where you give a prepared buffer).
With the messages defined, you can manage your buffers inside the callback function, without external initialization or destruction or pre-fill.
Moreover, streams have a user information field FMPI_STM_USER that you can use to store information about the streams buffers, so you can use this and a single callback function for all your streams.
aha99 2003-09-17
- 打赏
- 举报
流文件传送，一边传一边放
andysl 2003-09-16
- 打赏
- 举报
一个电影文件很大的。用 Winsock控件得传多长时间啊。美萍VOD可很快啊。
wzucdos 2003-09-14
- 打赏
- 举报
这并不需要什么网络共享
wzucdos 2003-09-14
- 打赏
- 举报
是通过winsock控件将视频文件传到客户端的
