Gateway

As an ISV or OEM today, you are faced with many challenges in deploying applications for network gateways. How do you build a gateway that is flexible enough to handle the diverse needs of modern clients? How do you provide a solution that is scalable and predictable under load? How do you support new application logic for diverse and numerous network services without requiring expensive application modifications? How do you tie together different data models, semantics and syntax in a distributed environment? How do you build an application framework that can adaptively adjust "how" it delivers content based on "what" type of content is being delivered and "what" type of device is consuming the content?

To address these questions, OEMs and ISVs building applications for network gateways have had no choice but to build complex infrastructure to support their application logic.

While the challenges are daunting, there is an answer: Implicit's RADkit. Our RADkit provides a complete infrastructure that not only addresses these challenges but enables OEMs and ISVs to build, deploy and maintain applications for network gateways better than ever before.

Challenges with existing infrastructure:

  • No support for dynamic binding of application logic/li>
  • Poor scalability and poor performance under load
  • Difficult to deploy and maintain in heterogeneous environments with disparate backend, network and web services
  • Platform/OS dependencies
  • Inefficient processing of content requires over specification of hardware resources
  • Limited support for content-type based QoS management
  • Limited support for active discovery of client resources

Benefits of using Strings:

  • Applications logic bound at runtime for the ultimate in flexibility
  • Highly scalable for maximum throughput and predictability under load
  • Embrace heterogeneity by dynamically adding application logic at runtime without requiring costly modifications
  • Platform independence allows for deployment on UNIX or Windows based servers
  • Optimal processing of content squeezes the most out of hardware resources
  • Content-type based QoS management allows for proper processing of time sensitive content such as video and audio
  • Deliver content based on actively discovered client resources, such as screen size and processing power