Prepare for a Lively SOA ?Request-Reply? Debate

Login or Register for Dates, Times and to Reply

Thread Tools Search this Thread
# 1  
Prepare for a Lively SOA ?Request-Reply? Debate

Tim Bass
Thu, 27 Sep 2007 22:34:57 +0000
It looks like the event processing blogosphere is about to be energized with a lively discussion.**** Opher has opined that SOA is not inherently request-reply.*** Pen to paper!** Let the lively debates begin!
Kindly turn your attention to IBM’s discussion of SOA and their figure below.
The IBM*figure was derived from the original view of SOA, Register-Find-Bind,* found here*in a figure titled “SOA”.
Kindly notice that Bind, as defined by has a two-way arrow.** This is a request-reply architecture.
In addition, IBM*(from the link referenced above)*also defines these properties of an SOA:
CapabilityDescriptionLoosely coupled interactionsServices are invoked independently of their technology and locationOne-to-one communicationsOne specific service is invoked by one consumer at a time. The communications are bidirectionalConsumer-based triggerThe flow of control is initiated by the client (the service consumer)SynchronousReplies are sent back to the consumer in a synchronous wayEOP Image

Login or Register for Dates, Times and to Reply

Previous Thread | Next Thread
Thread Tools Search this Thread
Search this Thread:
Advanced Search

Test Your Knowledge in Computers #1000
Difficulty: Medium
Trusted Computer System Evaluation Criteria (TCSEC) is frequently referred to as the Red Book.
True or False?

4 More Discussions You Might Find Interesting

1. IP Networking

No reply to NDP request from Linux host

Hi, new here. We are attempting to prove that an application will be able to carry IPv6. All is fine with IPv4 but not so much with IPv6. For now, we're just starting to ping between hosts to ensure basic communication. I'll try to put as much info but of course feel free to ask for more. ... (4 Replies)
Discussion started by: SavLou
4 Replies

2. Linux

Linux-laptop compatibility debate

Hey guys, i use my mac laptop and i love it, but i have decided its time to break the mold and use linux, and since linux on macs suck, i need to know what kind of pc to build... I want to know what kind of motherboard, wireless cards, hard drives, laptops, video cards, and etc. people have had... (3 Replies)
Discussion started by: mesaynaysayer
3 Replies

3. Shell Programming and Scripting

getting stderr & stdout output lively modified

This is about getting all output to stderr and stdout localized. Nothing to do with redirecting output to a file (there already are some interesting threads about that issue on this forum). What I intend to do is capturing all lines of text sent to the screen, compare them with an array of... (2 Replies)
Discussion started by: teo ramirez
2 Replies

4. UNIX for Dummies Questions & Answers

FTP debate...

Hello, sorry in advance, I'm a first time poster and somewhat new to UNIX (Mac OS X) I've searched on your boards and have been unsuccessfull in finding information on this. I have found some info at Google but not enough to validate my stance in a debate. I'm trying to FTP into a server and the... (9 Replies)
Discussion started by: jonathanfreeman
9 Replies
xcb_sync_list_system_counters(3)				   XCB Requests 				  xcb_sync_list_system_counters(3)

xcb_sync_list_system_counters - SYNOPSIS
#include <xcb/sync.h> Request function xcb_sync_list_system_counters_cookie_t xcb_sync_list_system_counters(xcb_connection_t *conn, Reply datastructure typedef struct xcb_sync_list_system_counters_reply_t { uint8_t response_type; uint8_t pad0; uint16_t sequence; uint32_t length; uint32_t counters_len; uint8_t pad1[20]; } xcb_sync_list_system_counters_reply_t; Reply function xcb_sync_list_system_counters_reply_t *xcb_sync_list_system_counters_reply(xcb_connection_t *conn, xcb_sync_list_system_counters_cookie_t cookie, xcb_generic_error_t **e); Reply accessors int xcb_sync_list_system_counters_counters_length(const xcb_sync_list_system_counters_reply_t *reply); xcb_sync_systemcounter_iterator_t xcb_sync_list_system_counters_counters_iterator(const xcb_sync_list_system_counters_reply_t *reply); REQUEST ARGUMENTS
conn The XCB connection to X11. REPLY FIELDS
response_type The type of this reply, in this case XCB_SYNC_LIST_SYSTEM_COUNTERS. This field is also present in the xcb_generic_reply_t and can be used to tell replies apart from each other. sequence The sequence number of the last request processed by the X11 server. length The length of the reply, in words (a word is 4 bytes). counters_len TODO: NOT YET DOCUMENTED. DESCRIPTION
Returns an xcb_sync_list_system_counters_cookie_t. Errors have to be handled when calling the reply function xcb_sync_list_system_coun- ters_reply. If you want to handle errors in the event loop instead, use xcb_sync_list_system_counters_unchecked. See xcb-requests(3) for details. ERRORS
This request does never generate any errors. SEE ALSO
Generated from sync.xml. Contact for corrections and improvements. XCB
2014-06-10 xcb_sync_list_system_counters(3)

Featured Tech Videos