https://www.linkedin.com/pulse/loi-sony-xa-bi-hong-camera-va-nhung-dieu-nguoi-dung-nen-%C4%91i%E1%BB%87n-tho%E1%BA%A1i?

https://www.linkedin.com/pulse/loi-sony-xa-treo-logo-dung-may-trong-mot-nhac-%C4%91i%E1%BB%87n-tho%E1%BA%A1i?

https://www.linkedin.com/pulse/loi-sony-xa-bi-hu-hong-man-hinh-thay-m%C3%A0n-h%C3%ACnh-%C4%91i%E1%BB%87n-tho%E1%BA%A1i?

https://www.linkedin.com/pulse/man-hinh-sony-xa-bi-soc-va-nhung-dieu-nguoi-dung-nen-biet-%C4%91i%E1%BB%87n-tho%E1%BA%A1i?

The acl feature should work – it’s tested in the test suite – I would have to know more to be able to debug. Perhaps you could trace using firebug or something and see whats going on?

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?

Thanks Sean for quick response…
I am using SameDomainTransport and specified the acl in provider like as acl : “http://example123.com” now my consumer which is on loaclhost able to recieve the message which is wrong as per my understaning only http://example123.com domain would get message not others . Please correct if i am wrong.

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);
});

Could you be a little more specific? All the transports are reliable, so if you want receipts then you need to implement this on top of easyXDM’s transport channel (although I see no reason why).

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

You should continue this on easyxdm.net, or on the google group.
The ACL feature is pretty simple, this is copied verbatim from the docs (http://easyxdm.net/current/docs/?class=easyXDM.Socket)

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.