Closed philipashlock closed 11 years ago
The proposal for the Service Discovery Mechanism (#25) includes this, so this ticket could probably be merged with that one. The proposal is at: http://wiki.open311.org/Service_Discovery
Replying to [comment:1 philipashlock]:
The proposal for the Service Discovery Mechanism (#25) includes this, so this ticket could probably be merged with that one. The proposal is at: http://wiki.open311.org/Service_Discovery
Just testing the !TracBacksPlugin to make sure a reciprocal comment is made with ticket #25
I'm closing this ticket since it has been rolled into ticket #25
Many clients will cache services and service definitions, but if a service definition changes or a service is added or removed, the client will need to know this. It's been proposed that a unique identifier (which could be a timestamp or a hash of services/definitions) could be added to the service discovery mechanism so that the client can easily see whether it needs to reload services/definitions.
Topic Discussion: http://lists.open311.org/r/topic/4ZxuI5gGcAzX9yGzyDiyhL