|
Published Articles >> Table of Contents >> Abstract
January/February 2004 (Vol. 8, No. 1)
pp. 87-89
The More Things Change . . .
Steve Vinoski, IONA Technologies
Full Article Text:
   
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MIC.2004.1260709
Send link to a friend
| Abstract |
|
If applications were static, maintenance efforts primarily could focus on tracking down and fixing intermittent bugs that appeared only after days or weeks of continuous operation. Unfortunately, middleware applications rarely are static. Not only do changing business requirements impact the applications themselves, but for a variety of reasons, the various platforms, operating systems, and middleware underneath the applications also change. Dealing with versioning and change management in a deployed middleware application can be complicated and costly.
|
 References
|
[1] B. Joy et al., The Java Language Specification, 2nd ed., Addison-Wesley, 2000; http://java.sun.com/docs/booksjls/.
[2] D. Watkins, M. Hammond, and B. Abrams, Programming in the .NET Environment, Addison-Wesley, 2003.
[3] D.C. Schmidt and S. Vinoski, "Corba and XML, Part 1: Versioning," C/C++ Users J., vol. 19, no. 5, 2001; www.cuj.com/documents/s=7995cujcexp1905vinoski /.
[4] M. Henning, "A New Approach to Object-Oriented Middleware," IEEE Internet Computing, vol. 8, no. 1, 2004, pp. 66—75.
|
 Additional Information
|
Index Terms- versioning, object, message, distributed, middleware
Citation:
Steve Vinoski,
"The More Things Change . . .,"
IEEE Internet Computing,
vol. 8,
no. 1,
pp. 87-89,
Jan/Feb,
2004
|
|
RSS Feed