Web Services Architecture and Its Specifications [Electronic resources] : Essentials for Understanding WS-* نسخه متنی

اینجــــا یک کتابخانه دیجیتالی است

با بیش از 100000 منبع الکترونیکی رایگان به زبان فارسی ، عربی و انگلیسی

Web Services Architecture and Its Specifications [Electronic resources] : Essentials for Understanding WS-* - نسخه متنی

Luis Felipe Cabrera, Chris Kurt

| نمايش فراداده ، افزودن یک نقد و بررسی
افزودن به کتابخانه شخصی
ارسال به دوستان
جستجو در متن کتاب
بیشتر
تنظیمات قلم

فونت

اندازه قلم

+ - پیش فرض

حالت نمایش

روز نیمروز شب
جستجو در لغت نامه
بیشتر
لیست موضوعات
توضیحات
افزودن یادداشت جدید





Resource Information


When querying for and updating information about our drinking fountains, WS-Management leverages WS-Transfer and WS-Enumeration. WS-Transfer provides mechanisms to create new registrations within the Resource Manager, and the read and update operations are useful for requesting, reporting, or changing the state of our resources.

To show how this works in practice, we use a scenario of retrieving and updating information about one of our smart fountains and then add the announcement and registration of a new fountain on the network. Figure 17-1 shows the message exchange for our sample scenario.


Figure 17-1. Managing resources.

    The Manager requests information about a known drinking fountain by sending a Get message [Message 1] to a known management agent. The Agent replies with a GetResponse message [Message 2] that contains the current information about the fountain.

    The Manager determines that the current temperature setting for the fountain is too high and sends the agent an updated XML representation for the fountain through a Put message [Message 3], which the Agent then uses to reconfigure the fountain. When successful, the Agent responds with a PutResponse message [Message 4].

    When a new fountain connects to the network, it uses WS-Discovery to send a Hello message [Message 5] to the network. This information is then used by the Agent to put a new entry for the fountain in the control system via a Create message [Message 6] with it's corresponding CreateResponse message [Message 7] containing resource details.

    The Manager retrieves the current list of fountains on the network through WSEnumeration. Enumerate and EnumerateResponse messages [Message 8 and Message 9] are exchanged to set up the enumeration context; a Pull message [Message 10] is then used to retrieve the fountain list.

    Once the last information in the sequence is retrieved, the enumeration context is released and confirmed [Message 11 and Message 12]. The specific underlying messages are not shown, because they would be a repeat of what we saw before.

/ 130