Technology

Reqwireless builds development libraries and applications for mobile Java devices. The development libraries are rich interfaces that enable development of capable applications on mobile Java devices. Applications such as WebViewer, EmailViewer, GotMailViewer, and HotViewer, use these libraries to bring a rich web and email experience to mobile Java devices.

Reqwireless Architecture:

Reqwireless uses a split architecture, where each Reqwireless development library has a client and middleware component. The client resides on a Java mobile device supporting J2ME/MIDP, the middleware resides within any Java application server. The development library or application communicates only with the middleware component to perform the required actions to complete the client request.

Each Reqwireless development library or application uses the Reqwireless middleware component to perform the computationally intensive tasks. For example, a request to the ReqwirelessWeb library to fetch an HTML web page for display will result in the middleware receiving a request from that client containing the URL to fetch and the characteristics of the requesting device (the height/width of the screen, and color capabilities). The middleware is then able to use its considerable computing resources to fetch that page and create a version of that page structured for display with those characteristics. The other Reqwireless development libraries use this middleware component in a similar fashion. The middleware component is available as a series of Java servlets. This allows the middleware to seamlessly integrate with existing Java application-server infrastructures, such as IBM WebSphere, BEA WebLogic and Apache/Tomcat. As Java application servers are available for virtually every modern operating system, the Reqwireless middleware component can exist on virtually every hardware/operating-system configuration available.

Key Advantages:

Reqwireless’s proxy-based architecture provides two key advantages over pure client-side applications on mobile devices:

* Smallest Client Size: By implementing much of the application logic on the middleware component, client application sizes are kept to a minimum. Consider the feature list of WebViewer. No other microbrowser can come close to supporting this much rich functionality in only 50 kilobytes. Accordingly, Reqwireless-based applications easily fit on some of the most space-constrained mobile devices on the market today.

* Fastest User Experience: The proxy-based architecture enables the fastest end-user experience through several factors. The dedicated middleware does the “heavy lifting”; it can clearly execute most tasks far more quickly than is possible on a mobile device (by extension, Reqwireless-based applications are less of a drain on a mobile device’s battery). Additionally, smart application design can reduce unnecessary wireless bandwidth usage, resulting in much faster response times for the user. For example, pure client-side applications are forced to individually retrieve full-size images and transform them locally for display. By contrast, WebViewer, EmailViewer, GotMailViewer, and HotViewer can scale down images on the proxy and deliver the appropriate thumbnails instead. Over wireless links, these factors all contribute to the fastest end-user experience, easily seen when compared to pure client-side applications of similar functionality.