Abstraction of astdb writes in web interface

(from #1368:)

11/16/06 08:57:37 changed by p_lindheimer

while you are at it - you should actually be doing the same thing with updating astdb variables because otherwise the perceived separation of configuration changes and THE RED BAR isn't really there. In other words, extensions writes to astdb variables, followme and many others. So as soon as someone clicks submit, the pbx is in a partial inconsisten state until they apply. So what you really need is a transaction log that can be applied by retrieve_conf or similar, for anything that would change the state of the machines and generate a reload. This includes adding, deleting and changing astdb variables, file changes, etc. Voicemail would have to be looked at carefully - this one is a bit volatile and needs some thought.

Greg, while I agree (having discussed it with you) we've been doing this since forever and I don't think there is anything that is to severe (or we would no about it). So I'm going to move this to 2.3. It is a big change and we are trying to stablilize so we can ship and move on to 2.3 where we can properly address it.

Milestone 2.3 deleted

moving to 4.0 Milestone, about the time that we have bigger changes ala daemon, etc.