<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://gregmckinley.com/cs/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Primitive Computing</title><link>http://gregmckinley.com/cs/blog/archive/2006/06/26/15.aspx</link><description>Here is a use case for an enrollment process: 
Scenario X - Error: No Response to enrollment request 
1.&amp;nbsp; The customer clicks the enroll button. 2.&amp;nbsp; System X sends the enrollment request to System Y, but there is no response. 3.&amp;nbsp; The</description><dc:language>en-US</dc:language><generator>CommunityServer 2.0 (Build: 60217.2664)</generator><item><title>re: Primitive Computing</title><link>http://gregmckinley.com/cs/blog/archive/2006/06/26/15.aspx#25</link><pubDate>Tue, 05 Sep 2006 13:10:54 GMT</pubDate><guid isPermaLink="false">9f8fffc3-80f6-44ee-b09b-68af0d4418c5:25</guid><dc:creator>Jack</dc:creator><description>Hopefully, it is a rare case where the other system fails to respond. &amp;nbsp;If there were a &amp;quot;backup&amp;quot; system, such as an email with Tx details is sent instead in the background, then the transaction can complete - and the user would never know there was a problem. &amp;nbsp;Of course, this is an issue if you require real-time feedback.</description></item></channel></rss>