Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.

Monitoring Room Bandwidth and Locking Rooms

Avatar

Former Community Member

Hello everyone!

I have a question about room bandwidth that is crucial to our site design being practical and cost effective.

When a user/customer signs up on our web site, a room will be created programmatically for them and they can use it whenever they sign in.

Once a room is set up, is there any way to programmatically monitor it so as to watch bandwidth/costs and lock the room when a certain bandwidth limit is exceeded?  What we want to do is allow each user to have a cost limit (similar to the LCCS developer account limit of $15), and when they exceed it the room is locked until we unlock it.  I would love to use a server side script like PHP to do this.  Can a Flex app. even run quietly in the background and do this?  I apologize if I`m missing something and looking at this the wrong way.  We are just terrified that a malevolent user might somehow use his/her room for a purpose other than for what it was intended, or overuse the room, and drive our costs through the roof!

Thanks in advance for all your help and keep up the good work guys!

Matt

4 Replies

Avatar

Former Community Member

Hi Matt,

I tried googling "lccs create rooms on the fly" :

http://www.google.com/search?q=lccscreateroomsonthe+fly

and it led me right to Chapter 6 of the LCCS Developer Guide. I'll leave

the reading to you =).

For your second question, we don't have any APIs for monitoring bandwidth.

This is something we're definitely thinking about; in the meantime, you can

set the usage cap of your application (a whole set of rooms) to prevent your

bill from ever going over what you're able to pay. Likewise, you can monitor

your rooms for activity (whether or not there are users active, and how many

messages they're sending) using the hooks in the server-to-server APIs (see

chapter 7 of the dev guide).

Ultimately, the best way to prevent abuse is to focus on authentication,

and come up with your own login so that it's non-trivial for a hacker to

access your LCCS rooms. Chapter 6.4 has the details for this.

nigel

Avatar

Former Community Member

Hi Nigel!

Thanks for the info.!

Yeah, about 5 minutes after posting my original message, I had a nagging feeling I had read about the programmatic provisioning somewhere before.  I checked the Developer Guide and sure enough, there it was!  I went right back into the forum and changed my post =)  Sorry to waste your time with that one!

I just had one more quick question.  Is there a way to limit the amount of users in a room at one time.  I want to limit the amount of people that can be logged into the service at one time to 2 (or 3).  The way my rooms are set up, there is a host with his own application and one guest with their own application.  The host application has a roster and a couple of other controls that the guest should not have.  When the guest enters the room, he has to knock and be allowed into the chat by the host.  Having this setup should also have the side effect of reducing bandwidth costs as well.

Thanks again Nigel!

Matt

Avatar

Former Community Member

Hi Matt,

You can set the user limit on the room (see the room console's "manage"

tab, or RoomManager), but not at the account level. You could use server

APIs every time a user wants to come in, and check your pool of rooms to see

how many people are in them (I think Raff can elaborate), and just not allow

the user in if you have too many in the account.

hope that helps

nigel

Avatar

Level 1

Hi Matt

it`s can be php function getRoomInfo()

return xml

<result>

<status code="ok"/>

<meeting-info>

<name>na2-sdk-a6808cea-1ebf-49dc-a652-d0ad41c1c/yuor room</name>

<meeting-session-id>dacd1d79-e73c-4e8f-a3ca-9c0f7f1d3</meeting-session-id>

<fms>fms1.acrobat.com</fms>

<host>iadadobcnwa06p</host>

<is-connected>true</is-connected>

<user-count>1</user-count>

<account-id>na2-sdk-a6808cea-1ebf-49dc-a652-75aad41c1c</account-id>

<account-ident>na2-sdk-a6808cea-1ebf-49dc-a652-750ad41c1c</account-ident>

<application-id>na2-sdk-a6808cea-1ebf-49dc-a652-75aad41c1c/your app</application-id>

<total-bytes-up>28312</total-bytes-up>

<total-bytes-down>202263</total-bytes-down>

<total-messages>18</total-messages>

<total-connection-reported>1464910</total-connection-reported>

<total-bytes-reported>99600</total-bytes-reported>

<total-messages-reported>18</total-messages-reported>

<total-connection-time-reported>234250</total-connection-time-reported>

<peak-users>3</peak-users>

<date-created>Sat Apr 30 03:35:36 EDT 2011</date-created>

<date-started>Sat Apr 30 03:35:38 EDT 2011</date-started>

<date-ended>NULL</date-ended>

<date-expired>NULL</date-expired>

</meeting-info></result>