Hi there,
Unfortunately, subscribing at a node level isn't supported because it will
take us quite a bit of work to get done. Thanks for thoughtfully presenting
your use-case to us - this does help us with prioritization. We're adding it
to the backlog, and if we hear more requests we'll bump up its priority, but
I'll be honest that we'll likely not get to this for a few months.
One way you could work around this issue is to implement your own version
of either custom fields or a user tracker. I'll walk you through some easy
steps to build a custom tracker.
1. In the Room Console, create a new CollectionNode in your room. Name it
"customUserTracker".
2. Create a new Node in that collection named : "trackingNode".
3. Configure the node :
a) userDependentItems = true; // all items will auto-retract as the
publisher leaves
b) accessModel = 100; // will keep all publishes private, just your
server will hear them
c) publishModel = 10; // everyone can publish
Next, you'll need a bit of client code so that when a user joins, they
publish an "I'm here" message. Only your server will hear this because the
accessModel is set to 100 (OWNER, which your server is).
protected var customUserTracker:CollectionNode = new CollectionNode();
// run this when users enter the room
protected function someInitFunction():void
{
customUserTracker.sharedID = "customUserTracker";
customUserTracker.subscribe();
customUserTracker.addEventListener(
CollectionNodeEvent.SYNCHRONIZATION_CHANGE, onSyncChange);
}
protected function onSyncChange(p_evt:Event):void
{
// notify the server of arrival
if (customUserTracker.isSynchronized) {
// send an item to our node, use myUserID for the itemID.
var item:MessageItem = new MessageItem("trackingNode","",
ConnectSession.primarySession.userManager.myUserID);
customUserTracker.publishItem(item);
}
}
.. And that's it! Hook up your server to listen to "customUserTracker", and
you'll receive messages whenever a user joins. Because userDependentItems
auto-retract when the publisher exits, you'll get the retractions on exit as
well, without all the custom user field overhead.
hope that helps,
nigel
