Hi,
I've been wondering: what is the use case of the "lifetime"
in SLP?
RFC says:
> Clients indicate that they want URLs to be automatically
> refreshed by setting the usLifetime parameter in the SLPReg()
> function call to SLP_LIFETIME_MAXIMUM. This will cause the API
> implementation to refresh the URL before it times out.
Say I have a SA that provides service x, and it dynamically
registers for 300s. So far it seems this means that service is
likely to disappear after 5 minutes. OK, but the spec speaks
about refreshing: who will do the refreshing?
Can a good soul shed some light on this?
Another example, I have a static registration with this record
in /etc/slp.reg:
sevice:http://myservice/,en,10000
what does that mean? From what I've read I understand that
setting this to 65535 will have the service registration last
forever (until slpd exits).
But why would I want to use anything else?
Thanks,
aL.
--
Alois Mahdal <amah...@redhat.com>
Platform QE Engineer at Red Hat, Inc.
#brno, #daemons, #openlmi
------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls.
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
Openslp-users mailing list
Openslp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openslp-users
