Re: RFC : Interop Registration & Notification Service
Sounds an excellent idea to me. Are you also going to implement a web
interface to the registration?
--- In soapbuilders@y..., Simon Fell <soap@z...> wrote:
> This is an idea i've been kicking around for a couple of weeks, let
> know what you think.
> I've was thinking about how i could further automate the interop
> testing process, and at the same time make it easier to keep up with
> the stream of new & updated servers to test, client results to check
> for new problems. I came up with a normal service registration
> but extended it with a notification service (all SOAP based of
> course). The basic structure is this
> 1. Services
> We define 1..n services, we currently have the standard interop
> and it looks like there's at least one more on the way
> 2. Server Implementations
> You register a server implementation of a service, if you deploy an
> updated implementation, you register an update.
> 3. Client Results
> You register your client results page, each time you update your
> results, you register an update
> 3. Notifications
> You can register to be notified via a SOAP callback, each time there
> is a server and/or client change, this would enable you for example
> re-run your client test suite against that service.
> In addition to the SOAP based stuff, the log of client and server
> updates could populate a RSS feed and/or a digital dashboard
> Whilst i don't want to complicate the interop process, i feel at
> point, a little infrastructure will make everyone life a little
> I posted some WSDL files, of what i thought the SOAP interface might
> look like at
> http://www.pocketsoap.com/registration/service.wsdl ( core service )
> http://www.pocketsoap.com/registration/notification.wsdl ( the
> callback interface )
> If people feel like this is worth pursuing, then i'm more than happy
> to develop & host the service.