Comments on: The Response Pattern

By: Jacob Wright

Jacob Wright — Mon, 31 Aug 2009 18:16:32 +0000

The way I’ve described it is different than the IResponder method. It allows you to chain and reformat data. If it was exactly the same I wouldn’t have posted about it at all.

By: Si Robertson

Si Robertson — Sun, 30 Aug 2009 16:40:46 +0000

Very good article. However, the use of Responder classes is not a new concept and you have more or less described the functionality of the mx.rpc.Responder class as Tyler^ mentioned. I have been using Responder classes myself for a couple of years now.

responder = new Responder( onResult, onError );
service.doSomething( responder );

function onResult( data )
{}

function onError( data )
{}

Passing a responder to, or receiving a responder from, a service (or anything else) doesn’t make any difference to the functionality or end result.

By: Jacob Wright

Jacob Wright — Sun, 23 Aug 2009 16:38:03 +0000

Yes, it is similar to IResponder and AsyncToken but like callback it takes methods/functions (less coding). It also allows for sync/async operations. I will post some code soon that shows my implementation of Response in action.

By: Not that Tyler

Not that Tyler — Sun, 23 Aug 2009 00:46:45 +0000

I've been following both your blogs for a while, and hadn't thought that you two where related, let alone twins. :) This sounds like the flex mx.rpc.IRsponder and mx.rpc.AsyncToken from the flex framework. It is an variation of the callback method, using classes instead of functions. The AsyncToken can hold multiple IResponders, and calls them at the completion of the Async event. As I understand it, this is the recommended pratice for working with remote data in Cairngorm as well.