Forums

Great congratulation !

One question how could we see our quota usage in chat and presence message vs the rest ?

- Our 'Test' Edoboard button may stay to try the plateforme 'interface' only without AFCS connection.We were using AFSC even for the non shared demo.

- The largest cost is connection time, we should add a 5 min inactivity timer to auto disconnect the user.

hum .. I was reading 1cens a minute my bad.

Otherwise it seems very afordable great !

Greg

Great congratulations to LCCS team!

BTW, are there any new features available along with 1.0 SDK released?

I checked the release notes but only found the update for 0.94 and earlier.

Thanks!

Jinni

Can you give an example of how the "Live Stream Bandwidth" cost (non-P2P) would be applied, i.e.:

  - 1 host and 1 participant using video for ten minutes streams X amount of up and down bandwidth, costing $XX

  - 1 host and 1 participant using video AND audio for xx minutes...costs $XX

Also, where does the whiteboard fit in this, as a "Push Message"?  If so, an example cost of using Whiteboard, if applicable.

I think this would be very helpful for those (like me) who aren't familiar with the type and amount of actual data passing through the service.

Hi, Fang/Nigel.

Any further thoughts on "behind the firewall" deployments of ALCS?

Thanks,

Rick Bullotta

Burning Sky Software

Bandwidth is bandwidth is bandwidth (and the term "live stream bandwidth" is confusing.

We count the size of the data sent and received (including data messages), so if for example you are transferring images as data messages they will count as bandwidth used.

User time is calculated as the total connection time of each user, so if you have one user connected for an hour and then another user joins for 30 minutes you will have 1h 30m of user time. Also, we bill for the total connection time for the month, so if you have users connecting to the rooms for only a few minutes at a time they will still contribute to your total connection time for the month and you will be billed for it.

Of course if you don't convert any application to "paid" you can still use the system for the equivalent of $15 of usage per month, so the best thing to understand how the pricing model work is to run some test application and check the usage.

Hi Izunna,

  You will incur a little bit of messaging hit for joining the room and publishing your presence (UserManager pushes a message to others in the room). A list of messages incurred by the framework itself is a good idea - we'll look into getting that documented. In general, it should be a pretty tiny amount of your cost.

  thanks

   nigel

We still have a free offering available for development and non-commercial use. With the new quota system you get $15 worth of free usage a month and if you need more or you want to bring your application commercial you can upgrade your account and select which applications you want to pay for and the maximum montly payment / usage you are willing to incur.

Great, thanks for the post!  And, with P2P, almost nothing!

David

Wow, thanks guys. That is massively awesome.

So basically, I wont even need to build a separate solution for Adobe Stratus to use P2P, but it is built into LCCS.

Fantastic.

Thanks!

I am not sure I understand your question completely.

BinaryPublish publishes a binary "file" to our temporary local repository, so while you can upload a small video and share it (via download) for the duration of a session I don't think it's what you want to do in your use case.

NetGroup is one of the p2p features that will be available in FlashPlayer 10.1

LCCS does support p2p connections and p2p a/v streams and it will use the NetGroup feature for data sharing between peers (I think, I am not familiar with that part of the code, but in any case we will provide p2p data sharing when 10.1 will be available)

We are adding p2p data sharing to LCCS, that uses the same primitives you use to connect to Stratus and then establish p2p connections to peers (and we'll be using NetGroups to group peers)

So, yes, you'll be able to write p2p applications for data messaging that use the LCCS data messaging model. But you will not be able to reuse your low-level code you wrote for Stratus, since we don't expose the NetConnection interface.

The nice thing of using LCCS vs. Stratus is that your application can leverage both client-server and p2p configuration depending on the number of user connected and network conditions. Or, you can start with client-server configuration and then switch to p2p if you find out that your typical use case is, for example, a few users mostly on the same local network. Or start with p2p and later reconfigure for client-server if your typical use case is a large number of users, or users that normally are on networks that don't allow or perform poorly in a p2p configuration.