感谢!

我参赛的作品是《FMS视频直播系统》，发在“参赛作品”区的“视频类”中，请大家支持我！

因为参赛网页对作品的简介有字数限制，发不全，因此，您可以直接点这里看系统简介。

看完简介后，如果您感觉该系统还可以，不要忘了投我一票，地址是：http://adobec.csdn.net/works/showDetail/312。

有图有真相，谢谢！

1、观看的人越多，越流畅。

2、可以部分解决打洞问题，在线人越多的时候，原来观看不到视频的客户端有可能观看到视频。

感兴趣的同行可以测试一下。

说明：根据Adobe工程师写的教程演变而来的例子，改成了Flash CS5版本。

用法：直接单击播放按钮，要稍等一会，文件块下载完毕后会自动播放(文件大约12M左右)。

File Sharing over P2P in Flash Player 10.1 with Object Replication

*Note: this intro article will be followed by other Object Replication concepts and practices

Object Replication

Object Replication is the most lowest-level P2P access available in Flash Player 10.1 (followed by Multicast, Posting and Directed Routing). It basically enables you to send chunks of data between peers. Object Replication is the only P2P access method that guarantees that all data will be transferred to all receiving peers.

Demo

I’ve built this simple file sharing application, which basically loads a file and then you start sharing it. Open another client to start receiving the file.
 

How to use it:
Open a provider in one window - browse for a file (JPG, PNG, GIF). Once it’s loaded, it will start sharing the file. Open a receiver in many other windows and start receiving. Provider and receiver are included in one app in this example.

How does it work

A classic scenario for Object Replication in Flash is file sharing. You have two clients, one is sending the data (Provider) and the other one receives the data (Receiver). You were able to do this already in Flash Player 10 using NetStream - but this worked only for two clients and there where no replication of objects to the members of a group => Massive File Sharing! In our scenario, you can have thousands of receivers.

Provider
Provides data for others. This is the originator. First you need to have an object with data you want to share. You most probably will load a file using URLStream or FileReference. Then you need to split this file into separate ByteArray chunks and give them indexes (it can be an indexed array). Keep the chunks reasonably small to avoid transfer issues (around 64KB). So if you load a 2 MB file, you will have 32 chunks. Finally call NetGroup.addHaveObject(0, 32); which says you have in this case 32 chunks available for others.

Receiver
Receives data from a provider. Here you just call NetGroup.addWantObjects(index, index); and start receiving objects from the provider. I do this by keeping the increasing the index by 1 once received a chunk. So you basically call NetGroup.addWantObjects(index, index); 32 times. When you call addWantObjects, the Providers gets a status “NetGroup.Replication.Request”. At this point the provider needs to write data to a group using NetGroup.writeRequestedObject(event.info.requestID,chunks[event.info.index]). Once it writes the data, the Receiver gets a “NetGroup.Replication.Fetch.Result” status event and save the data locally to an object. Remember, that the Receiver is just receiving data, it is not providing the data to other peers. After it has received all chunks, the Receiver just goes through the chunks and put them together into a final ByteArray.

Receiver/Provider
So why not to provide the received data to other peers to make the trasfer faster and maybe more stable. Once you receive some data using NetGroup.addWantObjects(index, index); and save them in “NetGroup.Replication.Fetch.Result”, you can start providing the data to other peers using NetGroup.addHaveObject(index, index);.

Of course there is lot more to be done, but first let’s have a look at this schema for the above.

Simple Object Replication

To demonstrate how Object Replication works, let’s try this second demo. In this example you have an object, which we fill with and array of 100 elements. Then start sharing this array. Run the second client to start receiving the array.

Provider peer:
1. Once connected, click fillObject
2. Then click addHaveObjects
3. That’s all

Receiver peer:
1. Once connected, click addWantObjects
2. It should start receiving objects shortly
(there is a loop, first chunk you receive is count of objects, once you receive a chunk the index increases by 1 and asks for next chunk until they are all received)

There are couple more buttons - you can try playing with it a little bit if you want.

How was it built?

Once connected to a server setup a NetGroup instance like this:

private function setupGroup():void{	var spec:GroupSpecifier = new GroupSpecifier("myGroup");	spec.serverChannelEnabled = true;	spec.objectReplicationEnabled = true; 	netGroup = new NetGroup(netConnection,spec.groupspecWithAuthorizations());	netGroup.addEventListener(NetStatusEvent.NET_STATUS,netStatus);}

Once connected to a NetGroup, which means that user allowed P2P connections, UDP is enabled and so on - you do operations on a NetGroup. First set object replication strategy. We will be receiving packets one by one (moreless).

netGroup.replicationStrategy = NetGroupReplicationStrategy.LOWEST_FIRST;

In your netStatusHandler - catch two codes:

// This code is called on a Providercase "NetGroup.Replication.Request": 	// calling this causes "NetGroup.Replication.Fetch.Result" invocation on a Receiver	netGroup.writeRequestedObject(event.info.requestID,obj[event.info.index]) 	break; // This code is called on a Receivercase "NetGroup.Replication.Fetch.Result":        // received chunks can be already provided to others	netGroup.addHaveObjects(event.info.index,event.info.index);         // write a chunk into an object/array	obj[event.info.index] = event.info.object; 	if(event.info.index == 0){		// First chunk (0) holds the number of chunks		objSize = Number(event.info.object);	}else{		// Receive chunks until you are full		if(event.info.index+1<objSize){			netGroup.addWantObjects(event.info.index+1,event.info.index+1);			actualFetchIndex = event.info.index+1;		}	}	break;

The whole source code can be found here.

Creating ByteArray P2P File Sharing

By following the concept above it’s possible to load a file from disk or url and then start sharing it with others.

This explains how the first demo works.

For this I’ve split the application into four different classes:

LocalFileLoader.as
Loads a file using FileReference and splits it into chunks (~64 KB each).

P2PFileShare.as
Connects to Stratus and handles all Object Replication sending and receiving

P2PSharedObject.as
A simple value object, which holds the data (ByteArray), size, packetLenght, actualFetchIndex and chunks; it’s used by both classes above.

P2PFileSharing.mxml
The user interface, which puts it all together.

The complete source code can be found here.

The Provider should look like this after sending the data:

The Receiver should look like this after receiving the data:

In the next tutorial, I will look at how to use Object Replication with VOD video.

Where to go from here

Check other tutorials on P2P in Flash:

- P2P GroupSpecifier Class Explained In Details Part 1
- Multicast Explained in Flash 10.1 P2P
- Directed Routing Explained in Flash 10.1 P2P
- Simple chat with P2P NetGroup in FP 10.1

Video tutorials:
- P2P Chat with NetGroup in Flash Player 10.1
- Multicast Streaming in Flash Player 10.1 Tutorial

Tags: flash, Flash Media Server, flash player 10.1, fms, object replication, P2P, peer-to-peer, stratus
Posted in Tutorial |

1、观看的人越多，越流畅。

2、可以部分解决打洞问题，在线人越多的时候，原来观看不到视频的客户端有可能观看到视频。

感兴趣的同行可以测试一下。

技术使用Adobe Stratus+FMS+AIR.

点此下载体验(2010-7-22更新).

截图:

在开启Flash p2p 的组播功能时有两点要注意：

1、连接Stratus时的地址字符串应改为：

      stratusIP="rtmfp:";

     而不再是大家熟悉的：

     stratusPath="rtmfp://stratus.adobe.com/devKey/";

2、要给组绑定一个组播地址：

private function initGroups()
  {
   myGroupSpecifier = new GroupSpecifier("cn.fmser.group/1");
   myGroupSpecifier.multicastEnabled = true;
   myGroupSpecifier.postingEnabled = true;
   myGroupSpecifier.ipMulticastMemberUpdatesEnabled = true;
   myGroupSpecifier.addIPMulticastAddress("224.0.1.200:3000");
   myGroupSpec = myGroupSpecifier.groupspecWithoutAuthorizations();
   myNG = new NetGroup(myNC,myGroupSpec);
   myNG.addEventListener(NetStatusEvent.NET_STATUS,groupStatus);
  }

其余的发布播放跟大家熟悉的代码就没什么区别了。

史玉柱的3小时网上拍卖，竞价超200万元（腾讯科技配图）

腾讯科技讯（李松伟）6月16日消息，6月15日晚上10点，备受业界关注的巨人网络董事长“史玉柱的3小时”正式落槌，中标者为来自上海市的苏彦彬，他的出价是2001221元。拍卖纪录显示，在为期3个月的拍卖过程中，共有286位竞拍者叫价638次。

3月17日，“拍卖名人时间”栏目和优米网同时上线，首期拍卖的是巨人网络董事长兼CEO史玉柱的3小时，竞拍时间是3月15日-6月15日。该栏目历史叫价记录显示，在3月17日零点55分和58分有3起竞价，上午10点后竞价正式展开。在此后相当长一段时间里，“拍卖名人时间”栏目的知名度都超过优米网本身。

作为“名人拍卖时间”的幕后策划者，前央视制片人、因主持《赢在中国》而被大家所熟知的优米网创始人王利芬并不讳言该这一创意取自“股神”巴菲特拍卖午餐时间。

虽然无论是在个人知名度上还是在个人财富本身，作为“中国最出名的失败者”史玉柱与股神巴菲特都还有不小的差距，在最新一期的富豪榜排名上，两人的财富分别为145亿人民币和470亿美元。但拍卖的结果并没有两人个人财富相差的那么悬殊，在不久前刚刚落槌的最新一“顿”巴菲特午餐的价格是262.6311万美元，与之相对应的是史玉柱200.1221万人民币。

不过如果都比较第一次拍卖价格的话，史玉柱就要辉煌的多，因为巴菲特午餐第一次拍卖仅拍的2.5万美元善款。

不得不承认的是，无论炒作也好，做慈善也好，王利芬都抓住国人时下追星财富英雄的普遍心理，也让数亿网民知晓了自己创办的网络电视台优米网，这无疑就是一个巨大的成功。

在向媒体解释自己为何会“拍卖名人时间”时，王利芬曾说，“马云C2C的网站淘宝是淘东西，卖有形的物品。我这个要做的实际上是淘人们脑子中的智慧和经验。”

而在创办“拍卖名人时间”栏目后，她同时承诺会有更多名人会参与支持这一档栏目，史玉柱之后下一次拍卖哪位名人的时间，将由网民投票决定。

也许是巧合，在优米网所做的“你想和谁面对面”票选中，阿里巴巴董事局主席马云即以4060票高居第一，紧跟马云之后的就是被称为“究极华丽第一极品路人帅哥”的“乞丐王子”犀利哥，而优米网创始人王利芬则高居第三。

多对多模式：

二对一模式： 

 使用单位:广西教育厅就业指导中心  沃科网--河南省大学生就业创业服务平台

测试地址：

FMS版本:

招聘官(2vs1)      应聘者(2vs1)       招聘官(3vs3)      应聘者(3vs3)  

P2P版本:

招聘官(2vs1)      应聘者(2vs1)       招聘官(3vs3)      应聘者(3vs3)