About the errors;
from src/stack/RpcBehavior.js
…
try {
var result = fn.method.apply(fn.scope, params.concat([success, error]));
if (!undef(result)) {
success(result);
}
}
catch (ex1) {
error(ex1.message);
}
…
So the error should be caught and returned to the error handler – also, the test suite tests this, and it works.
What behavior are you seeing?

Other thing if am throwing exception like this below:
concatNames: function(a, b){

throw new Error(“foo error”);

}

do you think i should get message in the consumer error callback but i am not getting any error.
remote.concatNames(a1, a2, function(result){
var a3=result;
document.myform.add3.value=a3;
alert(a1 + ” + ” + a2 + ” EQ= ” + result);
},function(error){

alert(“error” + error);
});

What kind of errors are you trying to handle? easyXDM either works or it doesn’t – it’s pretty robust.

acl : Array/String
(Provider only) Here you can specify which ‘[protocol]://[domain]‘ patterns that should be allowed to act as the consumer towards this provider.
This can contain the wildcards ? and *. Examples are ‘http://example.com', ‘*.foo.com’ and ‘*dom?.com’. If you want to use reqular expressions then your pattern needs to start with ^ and end with $. If none of the patterns match an Error will be thrown.

If you have examples of this not working, then I would like to see the consumers domain, and the used ACL entry.