The work performed by a publish/subscribe system can conceptually be divided into subscription processing and notification dissemination. Traditionally, research in the database and networking community has focused on these aspects in isolation. The interface between the database server and the network is an aspect often overlooked by previous research. At one extreme, database servers are directly responsible for notifying individual subscribers; at the other extreme, updates are injected directly into the network, and the network is solely responsible for processing subscriptions and forwarding notifications. These extremes are unsuitable for complex and stateful subscription queries. A primary goal of this paper is to explore the design space between the two extremes, and to devise and present solutions that incorporate both database-side and network-side considerations in order to reduce the communication and server load and maintain scalability of the system. We focus on a broad ...