[Dev] Discovery Job

[Brett Wooldridge]

I think I'd prefer to kill the provider.  If there is a job doing the same thing I think it's better not to duplicate methods of achieving the same end in the API.  The same approach we took for backup/restore.  You gonna kill it, or you want me to?

-Brett

On 2/27/08 9:52 AM, "Leo Bayer" <lbayer at alterpoint.com> wrote:

Brett (et al),

I'm creating a server job for discovery so that we can have a singleton
schedulable discovery job.  As a side effect this means there will no
longer be a need for the Discovery Provider.  I'm going to change the
client to use create a job for interactive discovery.

 From an API standpoint, does it make sense to drop the Discovery
provider as it will no longer be used?  I know there is one example
script for ZipTie::Client that uses that provider that would presumably
be changed to create a job.  Do we need to worry about integrations, or
is it better to say that this particular provider is no longer supported?

 - Leo

_______________________________________________
Dev mailing list
Dev at ziptie.org
http://mailman.ziptie.org/listinfo/dev


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ziptie.org/pipermail/dev/attachments/20080226/9c4a7495/attachment.html