Content-based publish/subscribe removes limitations of the static topic-based flavor, but suffers from the dynamism it introduces. Besides making the reuse of existing multicast primitives problematic [OAA+00], content-based publish/subscribe is hard to express in an object-oriented setting. In this section, we illustrate the latter difficulty by outlining the limitations of existing content-based schemes.