On Mon, 2010-01-18 at 13:19 -0500, Dale Worley wrote: > On Mon, 2010-01-18 at 12:09 -0500, Marden P. Marshall wrote: > > In order to achieve the objective of realtime and granular > > dissemination, the database would utilize the postgreSQL Listen / > > Notify mechanism, in conjunction with table modification triggers. > > The application would then subscribe, i.e. Listen, for relevant > > database tables modification notifications. In response to the > > received notifications, the application would then query the database > > directly for the updated configuration. No more waiting for > > configuration files to be created / replicated and no more application > > restarts. > > It looks like this scheme requires that the application understand the > database schema for the data it is interested in.
I hadn't thought about that part, but that's an excellent observation. Direct access to the database means creating a coupling between the implementation of every service using this scheme and the database schema, which makes schema changes more difficult and more disruptive of development. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
