Accessing Devices Using a Web Service - Conclusion

(Page 5 of 5 )

With a little bit of knowledge and a relatively small piece of software (the example implementation is only a little over 400 lines of C++) we can provide a Web service.  Because of the very restricted nature of this implementation, we can provide this service in a very small footprint and with high security while still providing our customers with the information they need.  If we implement the Web service as a separate process, we can achieve small size, high security and robustness.  Such an implementation is provided in T. H. E. Solution’s PC on the factory floor toolkit (see http://www.the-solution-llc.com/development_tools.htm).  Like most engineering solutions, there are limitations.  The primary limitations are:

1. This solution is designed to support a relatively small number of connections (in the dozens not hundreds).  Because of the limited number of connections supported, client use of proxy web servers can cause a problem.
   
   
2. Obviously the limited number of connections makes the Web service highly vulnerable to denial of service attacks.  Part of the rational behind the two-channel remote access approach is to provide a separate “unknown” path for remote control access.
   
   
3. The XML used in this example is extremely simple in nature.  Many industry groups are developing specific rules and definitions for data interchange.  Specific applications should take advantage of such style sheets when they exist.
   
   
4. The examples all use a static IP address for the Web service.  This may or may not be a good solution for any specific application.  The requirement to support dynamic IP addressing can significantly complicate the solution.  This is especially true if the application’s environment only provides limited support for configuration and naming services such as DHCP and DNS.
   
   
5. The most complicated area of the web service concept, and one still very much in progress, is the means to dynamically locate web services and determine the nature of the service.  This has not been addressed at all for two reasons.  First, in all practical cases this would be handled exterior to the device.  Second, it is not at all clear that this type of registry capability is applicable to the problem we are trying to solve.

References

World Wide Web Consortium (W3C)
Specifications of numerous Web protocols including HTTP and XML
http://www.w3.org/

Matthew Powell and Leon Brackhnski
HTTP Revealed
Microsoft Interactive Developer, September 1996

David Cook
Write a Simple HTTP-based Server using MFC and Windows Sockets
Microsoft Systems Journal, February 1996

Microsoft Corporation
XML Tutorial
MSDN Library, July 2001

DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware.

Comments On: Accessing Devices Using a Web Service

>>> Be the FIRST to comment on this article!