GroupSpecifier is a very powerful class and ASDocs are good resource to look in, but I thought I’d write few more words on this topic since it’s easier to understand with a little more explanation.

postingEnabled and multicastEnabled
These are self-explanatory. Just a little note: the difference between Multicast and Posting is simply in the overhead used during their management. Posting should be used when you have lots of senders sending relatively little data (like Chat). Multicast when you have fewer senders sending lots of data (Video, Chat).

peerToPeerDisabled
Why should I disable P2P when I am building a P2P application? Obvious question. This one is for IP Multicast.
Application-Level-Multicast (so called P2P Multicast) is multicast established over peers.
Native IP Multicast is multicast enabled in the network - it must be supported by routers and the network itself.
Fusion is Application-Level-Multicast and Native IP Multicast used together.
So, when you disable P2P by saying peerToPeerDisabled=true, your app will use only Native IP Multicast, which is more efficient, but works mostly only in closed networks (like a company network).

serverChannelEnabled
Opens supporting functions from the server. In the basic scenario it enables auto-bootstrapping. Bootstrapping in this context means adding peers to the group. You can do this manually by calling the addBootstrapPeer function or setting serverChannelEnabled=true to make it automatic. In the P2P Chat example it basically takes care of adding peers to a group and establishes communication between them.

groupspecWithAuthorizations and groupspecWithoutAuthorizations
Difference? Security. If you set a posting or multicast password, the one “with” can post or multicast, the one “without” is receive-only.

Remember - GroupSpecifier is technically a String combined of properties and the name. If you change a property you will be in a different group.

More to come soon.

Go and watch it now!

.
Further reading:
Read the blog post by Phil McKinney (CTO for HP’s Personal Systems)

• Recording (Connect): http://my.adobe.acrobat.com/p44261112
• Presentation: Hello-P2P.pdf
• Source-code: Source-p2p-eseminar.zip

Links:

• Adobe Stratus
• RTMFP Groups on Labs
• Flash Player 10.1
• Developer Connection: Differences between Adobe Stratus and LiveCycle Collaboration Service
• Adobe LCCS

Tutorials:

• Video tutorial - beginning with P2P (FP 10)
• Creating Simple P2P Chat with NetGroup (FP 10.1)

Acapela created a SaaS (software as a service) offering for Text-To-Speech, which finally sounds pretty cool and I was quite amazed by it — even the Czech language is included This could be a very useful usability feature for your games. You can use it to read a story, chat messages, alerts and so on. I can even imagine this in your enterprise apps as a helper. I presume that having this functionality as a service can really reduce the size of your application (the voice bank must be huge) and CPU load, plus you also have all updates included.

They support ~20 languages in nearly 300 voice variations: Arabic, Czech, Danish, Dutch, English, Faroese, Finnish, French, German, Greek, Icelandic, Italian, Norwegian, Polish, Portuguese, Portuguese, Russian, Spanish, Swedish, Turkish.

Basic sample - more samples

* Built using my evaluation account - it should work till 25th March 2010

Basic code for retrieving voice from a string could look like this:

import com.acapela.vaas.BasicVaas;
import flash.media.*;
import flash.net.*;
 
var myVaas:BasicVaas = new BasicVaas();
 
myVaas.accountLogin = "your_account_login";
myVaas.applicationLogin = "your_application_login";
myVaas.password = "your_application_password";
 
myVaas.generateMessage("heather22k", InputText.text);
 
function messageAvailableEventListener(event:Event)
{
	var channel:SoundChannel = 
		BasicVaas(event.target).requestedSound.play();
}
 
myVaas.addEventListener(BasicVaas.MESSAGE_AVAILABLE, 
			messageAvailableEventListener);

- Acapela is a paid service, check pricing.
- API documentation (AS3).
- Check Acapela.tv

Flash Player: CPU Hog or Hot Tamale? It Depends.

Windows test results - check article for more - good reading

(Source: StreamingLearningCenter.com)

Free registration here (+ add event to your calendar)

Date: Wednesday, March 03, 2010
Time:

• 7:00 AM - 8:00 AM (San Francisco)
• 10:00 AM - 11:00 AM (New York)
• 3:00 PM - 4:00 PM (London)
• 4:00 PM - 5:00 PM (Prague, Paris, Barcelona)
• 7:00 PM - 8:00 PM (Abu Dhabi)
• 11:00 PM - 12:00 PM (Singapore)

Prerequisites for a successful seminar:
- Flash Builder 4 Beta 2
- Flash Player 10.1 Beta 3 debug version installed
- Flex 4 Framework

Meeting will be at this Connect room: http://my.adobe.acrobat.com/p2p-in-flash.

What if you don’t have a PC with you and still want to attend an online meeting. One of the features Connect Pro has is to connect people on a telephone via VOIP bridge so they can hear and participate by voice. But there are situations, when you want to fully attend the meeting via mobile.

Today Adobe introduced Adobe Connect Pro Mobile for iPhone, which you can download for free from iTunes. You can see the shared desktop (slides, pictures…), watch the live camera and chat. All simplified to fit the screen and usability on the iPhone.

Connect Pro is a nice example of a Contextual App - the app running the same context with adjusted user experience to fit the best on different devices.

All written in ActionScript 3.0
What’s even better is that Connect Pro and Connect Pro Mobile are both written completely in Flash/ActionScript 3.0. iPhone version is standalone app compiled to native bytecode using Adobe Packager for iPhone (available later this year). At Mobile World Congress 2010 we have announced AIR 2.0 for Mobile Devices and previewed Connect Pro Mobile running on Android (Motorola Droid). Which is simply the same code written and compiled in the next generation of Flash Pro to Android and iPhone. Android version was just a preview but it’s supposed to be available in the future for download as well. Together with this - AIR 2.0 is planned to be available in the second half of 2010. Basically you’ll be able to build your apps in Flash Pro by writing one base code and simplify porting to different devices.

Connect Pro running on Mac in browser, iPhone and Motorola Droid.

Video: iPhone apps built with Flash - showing Connect Pro Mobile

Farmville (popular Facebook game in Flash) running on the tablet

So why don’t you just take a ride with one these Flash Gaming Engines and push the limits of web gaming today.

You can also watch MAX 2009 session GPU acceleration in the new Flash Player.

Updated: 4:37 PM Feb 9 2010

Final demo: Try (run in few browsers) | Download source

Prerequsities:
- Flash Player 10.1
- UDP enabled network (you can’t be behind firewall, which blocks UDP)
- Flash Builder 4
- Stratus developer key - Get one here if don’t have already. You have to login using your Adobe credentials to get it.
- playerglobal.swc for Flash Player 10.1

Step 1: Create new Flex 4 project
File -> New -> Flex Project
Link new playerglobal.swc (FP10.1 API) to your project in Project Properties and set compiler version in Flex Compiler to 10.1.0

Step 2: Connect to Stratus
First of all we need to setup NetConnection to Adobe Stratus. That’s easy part.

private const SERVER:String = "rtmfp://stratus.adobe.com/";
private const DEVKEY:String = "YOUR-STRATUS-DEVELOPER-KEY";
private var nc:NetConnection;
 
private function connect():void{
	nc = new NetConnection();
	nc.addEventListener(NetStatusEvent.NET_STATUS,netStatus);
	nc.connect(SERVER+DEVKEY);	
}

Step 3: Setup NetGroup
We need to setup P2P group and connect to it. GroupSpecifier is a class, which let’s you to define all the parameters of the group. First you give it a name - in this case “myGroup/g1″. Then you set it to use serverChannel, to let it communicate with Stratus. Finally we enable Posting. That’s all you have to do to define the P2P Group.
Then we have to define the actual NetGroup. groupspecWithAuthorizations() returns String - it’s a group identifier. Now you probably ask, what’s the difference between groupspecWithoutAuthorizations() and groupspecWithAuthorizations(). If you set a posting or multicast password, the one “with” can post or multicast, the one “without” is receive-only.

private function setupGroup():void{
	var groupspec:GroupSpecifier = new GroupSpecifier("myGroup/g1");
	groupspec.serverChannelEnabled = true;
	groupspec.postingEnabled = true;
 
	netGroup = new NetGroup(nc,groupspec.groupspecWithAuthorizations());
	netGroup.addEventListener(NetStatusEvent.NET_STATUS,netStatus);
 
 
	user = "user"+Math.round(Math.random()*10000);
}

Step 4: Handle NetStatusEvent
We are going to handle at this step just three events. When we connect to Stratus we setup a group. When we connect to NetGroup we reflect it to UI and and when we receive a Posting message we show it in chat history.

private function netStatus(event:NetStatusEvent):void{
	trace(event.info.code);
 
	switch(event.info.code){
		case "NetConnection.Connect.Success":
			setupGroup();
			break;
 
		case "NetGroup.Connect.Success":
			connected = true;
 
			break;
 
		case "NetGroup.Posting.Notify":
			receiveMessage(event.info.message);
			break;
	}
}

Step 5: Sending and receiving message
We have to put together a message object, which handles text, user name, sender ID. Sender ID is useful to have for direct posting. And we also convert NetConnection PeerID to GroupAddress - participant address in the group. When we post() message to a NetGroup, we just distribute it/broadcast it, but it does not come back to us. So that’s why we need to call receiveMessage as well - to display it in history text field.

private function sendMessage():void{
	var message:Object = new Object();
	message.sender = netGroup.convertPeerIDToGroupAddress(nc.nearID);
	message.user = txtUser.text;
	message.text = txtMessage.text;
 
 
	netGroup.post(message);
	receiveMessage(message);
 
	txtMessage.text = "";
}
 
private function receiveMessage(message:Object):void{
	write(message.user+": "+message.text);
}
 
private function write(txt:String):void{
	txtHistory.text += txt+"\n";
}

Step 6: Create UI

<s:TextArea left="10" right="10" top="10" bottom="40" id="txtHistory"/>
<s:TextInput x="10" id="txtUser" text="{user}" bottom="10"/>
<s:TextInput left="145" right="88" id="txtMessage" bottom="10" enter="sendMessage()"/>
<s:Button label="Send" click="sendMessage()" enabled="{connected}" bottom="10" right="10"/>

Step 7: Run it

Find out what were the challenges and issues in creating a new Drupal Image Module using Flash and Flex technology. Get the inside tips from an Adobe Evangelist on what it takes to complete this kind of project, and stand a chance to win your own copy of Flex Builder* to help you get started with your development.
Walk through:

• Front end design of widgets and main page
• Back-end integration with Drupal
• Importing your libraries from Flickr and Picassa
• How to account for loading issues when having large libraries of images
• Why Flex and ActionScript where the technology of choice for such a project

Join Mihai Corlan for a 30 minute e-seminar on how this module was built. http://drupalimagemodule-evng.eventbrite.com