By Topic

Invocation styles

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$33 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

1 Author(s)

The terms static and dynamic exist in middleware, but they apply to very different concepts: we most often use them to describe different service-invocation styles - the nature of the information that a middleware application requires to properly invoke a given service. Just as engineering statics and dynamics play an important role in analyzing and designing real-world mechanical systems, robust middleware applications require static and dynamic styles of service invocation. what you need to know to invoke a service is: what to send to it, where to send what you're sending, and what the service will do for you. Here, I'll focus on "what to send".

Published in:

Internet Computing, IEEE  (Volume:7 ,  Issue: 4 )