Q: May I use my existing Boingo account in conjunction with a Wi-Fi handset that includes the new Boingo Embedded Wi-Fi Toolkit?
A: No. Boingo does not offer service for devices directly to end users; please contact your device manufacturer or service provider regarding such offerings.
Q: Does the Boingo Embedded architecture change anything about my Boingo As-You-Go or Boingo Unlimited account?
A: No. The Boingo Embedded architecture does not affect any of our laptop service offerings. You may use your existing laptop account(s) without any changes.
Q: Why should I sign up for a Developer Connection account on the Boingo Embedded site?
A: Anyone considering or even simply curious about the Boingo Embedded architecture should sign up for a Developer Connection account. Sign up takes only a minute and it is entirely free. Inside, you will find documentation for all portions of the Boingo Embedded architecture. In addition, you will also find tools that will help developers ensure proper interoperability of their handset with Boingo’s open source code.
Q: What is the difference between the open source and commercial code options of the Boingo Embedded architecture?
A: There are no feature differences between these two codebases. The only difference between these two items is how they are licensed.
The open source option requires that changes to the Boingo Embedded Wi-Fi Toolkit are republished publicly. That way, Boingo ensures that any unique features added to this code are available to the entire Wi-Fi market, encouraging adoption of the Boingo Embedded architecture across the industry. One should note that platform-dependent and user interface routines do not need to be republished under Boingo’s open source license plan.
However, Boingo realizes that some companies cannot use open source code in their development programs. In such situations, Boingo offers a commercial license that keeps all such development activities completely private and confidential. In order to support such projects, Boingo charges a moderate, volume-dependent royalty per handset using the Boingo Embedded architecture under this type of license.
Q: I represent a service operator and I want to offer the Boingo Roaming Network to my customers. Am I required to purchase the Boingo Configuration Server?
A: No. The communication channel between a Boingo-enabled Wi-Fi device and the Boingo Configuration Server is a standardized, open interface. You may download the appropriate APIs and documentation from the Developer Resources section of this site. As such, service providers are welcome to develop their own version of the Boingo Configuration Server independently.
That said, most service operators choose to purchase a turnkey solution from Boingo that includes the Boingo Configuration Server, along with integration assistance. Obtaining this system directly from Boingo assures service providers of an immediate go-to-market schedule free from unexpected engineering costs.
Contact
for additional information.
Q: I represent a handset manufacturer, how do I get started with integrating the Boingo Embedded Wi-Fi Toolkit onto my device?
First, open a Developer Connection account on this site and review the documentation. Next, download the source and technical specifications for the code from the boingowifitool project on SourceForge.net. In particular, review the Boingo Embedded Porting Guide document, as it will give you a clear understanding of the steps required to port the code to a specific platform.
General inquiries related to the Boingo Embedded Wi-Fi Toolkit should be sent to
Q: Why does Boingo use two different licenses for its open source offering?
A: Boingo carefully considered which Open Source Initiative (OSI) licenses it would use when distributing the Boingo Embedded architecture software modules. The Apache 2.0 license applies to the Application and Platform Abstraction Layers. This license allows licensees to customize these portions of the code without republishing requirements.
The main functionality of the Boingo Embedded architecture is found within the Boingo Embedded Wi-Fi Toolkit layer. This portion of code is licensed via the Lesser General Public License (LGPL) which requires the republishing of modifications made to this code. This way, Boingo is able to allow the open expansion and adaptation of this groundbreaking code without fear of multiple proprietary variations confusing the marketplace. In the spirit of the LPGL, licensees should design their implementation to dynamically link the Boingo Embedded Wi-Fi Toolkit layer so as to ensure that republishing requirements do not extend beyond that self-contained module.
