Summary
Event notifications are the lifeblood of an event-based system, so it is very important to choose the right type of delivery mechanism and payload. When notifications cross process boundaries, you have to be really careful about what kind of information is in the payload, because expensive marshaling might be involved. A common solution is to make use of lightweight business objects in notification payloads. These lightweight objects are sculpted carefully to exclude references to unnecessary user-defined types. Such lightweight objects can be passed across process boundaries with a minimum of overhead.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Patrick Th. Eugster, Rachid Guerraoui, and Christian Heide Damm, “On Objects and Events” (proceedings of the Conference on Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA), Tampa Bay, FL, October 2001).
Clemens Szyperski, Component Software: Beyond Object-Oriented Programming (Boston: Addison-Wesley Professional, 2002).
Jean Bacon, Ken Moody, John Bates, Richard Hayton, Chaoying Ma, Andrew McNeil, Oliver Seidel, and Mark Spiteri, “Generic Support for Distributed Applications,” IEEE Computer, March 2000.
Rights and permissions
Copyright information
© 2006 Ted Faison
About this chapter
Cite this chapter
(2006). Notification Payloads. In: Event-Based Programming. Apress. https://doi.org/10.1007/978-1-4302-0156-4_4
Download citation
DOI: https://doi.org/10.1007/978-1-4302-0156-4_4
Publisher Name: Apress
Print ISBN: 978-1-59059-643-2
Online ISBN: 978-1-4302-0156-4
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)