I'm not aware of any hard coded limit to the number of users supported, however at the moment, WIAB doesn't scale so you might find issues with a large number of users.
In terms of bandwidth, the base protocols are text over the wire, so each individual user should not represent a large chunk of bandwidth usage. Haven't done much in the way of measuring avg usage. For authentication, there is an interface which you can extend to build new authentication methods into the system. The currently supported authentication storage methods are: Memory File MongoDB However there is nothing that would prevent building an extension that say tied into a LDAP/Active Directories. Security is an issue at the moment as all communication between the client and the server is done via plain text, so anyone sniffing packets would be able to pick up passwords and usernames. That's my 30 seconds worth of thoughts, hope it helps. James On Wed, Mar 2, 2011 at 12:18 PM, Patrick Jennings <[email protected]>wrote: > Greetings fellow wave developers! > > I am currently working with a team that was asked to delve into the > possibility of using the Wave protocol in large classrooms. Currently, we > are looking into using Wave in a Box as a framework and are trying to find > any issues that may arise in releasing a future application that allows > students to collaborate via WIAB. > > It was brought to our attention that there may have been a hard coded limit > to the amount of active users to any given wave in previous implementations > or in Google's Wave. Is this the case with WIAB? Could anyone give a rough > estimate of the bandwidth requirements needed for say 100-200 active users > to one WIAB node? > > We realize that the current implementation is not ready for production and > is only meant to be a demonstration of the Wave protocol. Security and > authentication is another big concern for our group. If you have any > insightful thoughts or comments, please do not hesitate to share them as it > would be a great help to our team and the Wave community! > > Thank you, > > Patrick Jennings >
