Bogdan Brezoi wrote: > Damian Krzeminski wrote: >> Bogdan Brezoi wrote: >> >>> - a new web service will be hosted on sipXconfig , service responsible >>> for updating the discovered devices table in sipXconfig database with >>> new informations. This service will expose an update method which takes >>> an array of devices as a parameter and puts them into the database using >>> the newly created manager. >>> >> >> I think that in most cases the service will be called with a single >> device as soon as it's discovered. But of course supporting array/list >> of devices will work too. >> > After more thinking, i believe that there are 2 alternatives regarding > the operations published by the web service : > - if the service will be called in most cases with a single device as > soon as it's discovered, the a complementary delete method should exist, > and as soon as a device disappears, this method should be called in > order to remove the no longer existing device from the database. > - if each time a new device is discovered or an existing device is > removed from the net, the full list of existing devices in that moment > is passed to the service, then there will be no need to have an > additional delete method. The service will look in the database, remove > the no longer existing devices, update the existing ones and adding the > new ones. > > What do you suggest? > Bogdan >
I do think that there is a 3rd option: I'd like to make writing discovery agents as easy as possible and I want to be able to have more than one discovery agent running simultaneously. The agent should be stateless: it's not its concern that some devices 'disappeared' (which BTW only means that they are not visible at the moment when discovery is run). I think that sipXconfig should probably age out discovered devices that have not been added for some time, or maybe administrator should have an option to ignore the device once or forever (which would remove them from the list of discovered devices). But the discovery agent itself should just report everything that it sees whenever it is run. D. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
