WS-Dispatcher

Introduction
Authors
Why do you need WS-dispatcher?
Presentation
Download
Future Work
Contact

Introduction

WS-Dispatcher allows internal services to be safely exposed to Internet and allows clients that do not have endpoints to become true WS peers and supports intermittently connected clients that may be moving between networks.

Authors

Dispatcher was designed and implemented in Indiana University Extreme! Lab.

• Alexandre di Costanzo: detailed design and implementation
• Aleksander Slominski: general direction and design

Why do we need WS-Dispatcher?

• Do you use applets and want them to act as WS peers and be able to receive asynchronous messages such as notifications from WS-Eventing pr WS-BrokeredNotification?
• Do you need to expose in controlled manner internal web services and need failover, load balancing and robust store-and-hold functionality?

Papers and Presentations

Paper accepted for International Workshop on Java for Parallel and Distributed Computing during IPDPS 2005 titled "Asynchronous Peer-to-Peer Web Services and Firewalls" [PDF 185KB] describes WS-Dispatcher design rationale and performance evaluations. See also slides prepared for the workshop [PDF 245KB].

Generic overview of initial design: presentation [PDF: 24KB]

Download

Only in CVS (Make sure to read the license).

Future Work

We plan to experiment more with load balancing and use of WS-RM.

Contact

For more information, please contact authors .