Hi Alexander,
Am 13.03.2007 um 16:07 schrieb Alexander Weisser:
> Hi, thanks. I think it works, but now i have another problem.
[snip]
> Here is my initial method:
> qx.Proto.initialize = function(e)
> {
> // Define alias for custom resource path
> qx.manager.object.AliasManager.getInstance().add("custom",
> qx.Settings.getValueOfClass("custom.Application", "resourceUri"));
>
> var rpc = new qx.io.remote.Rpc(
> "http://localhost:8080/qooxdoo/.qxrpc";,
> "com.dkib.server.MyService"
> );
> rpc.setCrossDomain(true);
>
> for(var i = 0;i < 100;i++){
> // synchronous call
> try {
> var result = rpc.callSync("getValue");
[snap]
You can't issue synchronous calls in a cross-domain way, only
asynchronous ones. This is a technical limitation that we cannot work
around. Even within the same domain, synchronous calls are usually a
bad idea: They block the whole browser until the response arrives,
and when there's a network problem, the user may have to force-quit
the browser (or have great patience since the timeouts are usually
quite long).
Regards,
Andreas
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
