[MOBY] [MOBY-l] Interpreting results from Service->execute()

[Paul Gordon]

Or have a Time To Live associated with a service.  The policy would be 
central.  By default, a service stays listed for, lets say, 7 days.  
 From trusted domains you could make it longer.  Unless the provider 
sends a renewal message for their service, it disappears on the expiry 
date.  That way, you don't get cruft build up.  Those that want to 
provide services can at the very least send a message via the API once a 
month saying "we're still in business, and our service works!"

>
> Perhaps, the only way to tackle a piece of this problem is 
> periodically doing some tests on the service. Some of them could be 
> generic, like sending an ill-formed input or a correct object 
> belonging to an incorrect namespace. The others should be provided by 
> the service creator: two or three input objects which should give the 
> same output. Obviusly, many services will not have a deterministic 
> output, because they are based on a changing database, for instance. 
> But for these cases the service creators could notify 'our service is 
> still alive!'.
>
> You know, there is no easy way!
>
>     Best Regards,
>         José María
>