Wave in a Box as an open source communication platform has both advantages as well as disadvantages. Its advantages are worth mentioning. It is an all in one Wave server and thus a very rich web client. It is easy to install, in other words in various kinds of hardware and compatible with a wide range of system tools.
More importantly, Wave in a Box permits a federation between its (WiaB) servers, making the operations not only viable but faster. The software also helps to share waving and thus it is public. The strength of the software is in the fact that it is supported by Apache foundation.
The disadvantages of Wave in a Box include it being prone to bugs, even as it does not permit GWave features to be imported and it also does not allow users to implement contacts. The software also does not have playback facilities. It warrants an account that is wholly dedicated, and doesn’t have rights of moderation.
Some of the common features with other similar waves of Wave in a Box include collaboration and real time typing, it allows users to add or delete participants; even as conversations in threaded form can be carried on. On the flip side it does not have features which were present in Google Wave, and thus comparatively a lower-end software, and with its limitations to access.
There are only a few alternatives for Wave in a Box. They include Google Docs, which does not have OpenSocial Gadgets, while it partitions the documents, chats and comments. Google+ also doesn’t have OpenSocial Gadgets, apart from the absence of live typing and threaded comments. The other alternative is SAP Streamwork, which also doesn’t have live typing, and it is not free, and emphasis is on business orientation.
System administrators and IT managers should consider all factors before deploying any open source computing platform for communications.