• From: Fraser Goffin <goffinf@g...>
• To: xml-dev <xml-dev@l...>
• Date: Mon, 19 Jan 2009 09:17:07 +0000

Yes, and this also pre-supposes that a service will accept
'un-anticipated users'. In fact it might be worth your while
differentiating between services that do and don't.

For example, in SOA run-time governamce you might be pretty interested
in knowing whether there is any 'rogue' use of a service which may
impact its quality of service (QoS)
guarantees.

Fraser.

2009/1/19 Chin Chee-Kai <cheekai@s...>:
> Hi Roger,
>
> Nice summary and example!  Just that for the conclusion, are you able to
> elaborate just a little further on how to "monitor your web service and note
> changes in usage"?  I'm assuming you have some details and for the sake of
> conciseness, you've summarized them as "monitor and note".  I'm keen to hear
> how one could know the subset of information being extracted from the
> contents of your web service, and the type of users accessing (other than IP
> address) when the web service is offered to unanticipated users.
>
> Thanks.
>
> --
> Best Regards,
> Chin Chee-Kai
>
>
> Costello, Roger L. wrote:
>
> Hi Folks,
> ...
> Consequently, you need to monitor your web service and note changes in
> usage. This information will give you the knowledge of how to evolve your
> service to better accommodate your users.
>
>
>

• References:
  • Meaning of "Design for the unanticipated user"
    • From: "Costello, Roger L." <costello@m...>
  • Re: Meaning of "Design for the unanticipated user"
    • From: Chin Chee-Kai <cheekai@s...>