dannyst
07-01-2005, 04:30 PM
We are building a flash solution that needs to be tightly integrated with an already robust and fully developed .net environment.
We are using flash remoting to connect to the servers, and have run into an extremely unusual problem.
We built a functional solution that would succesfully access the .net environment as we need. Our connection addresses were all using localhost at that time.
var zipService:Service = new Service("http://localhost:80/project/Gateway.aspx",null,"SWFGateway.FlashLocations",null, null);
var pcZipCall:PendingCall = zipService.getStoreByZip(zip);
var pcZipCall:PendingCall = zipService.getStoreByZip(zip);
var pcZipCall.responder = new RelayResponder(_root, "getStoreByZip_Result","getStoreByZip_Status");
So as long as the address was at localhost and we were runing from localhost, it worked just fine.
However if we exchange localhost with the computer's network name, or its ip address then it breaks.
//obviously not the real ip address there
//we tried both the ip address and the name of the computer
var zipService:Service = new Service("http://1.1.1.1:80/project/Gateway.aspx",null,"SWFGateway.FlashLocations",null, null);
var pcZipCall:PendingCall = zipService.getStoreByZip(zip);
pcZipCall.responder = new RelayResponder(_root, "getStoreByZip_Result","getStoreByZip_Status");
Our IT admin people even tried setting up a web page in IIS for that computer and put the proper setups there. We could then browse to the default.aspx page in our browser, but flash remoting wouldn't work still.
We have been trying to figure this problem out now for a few days. So in a nutshel our flash remoting works only if our gateway is on localhost, and we are running on the same machine. The minute we change localhost to the ip address or computer name for that same machine, it breaks no matter where you run it.
Anybody know how to fix this?
We are using flash remoting to connect to the servers, and have run into an extremely unusual problem.
We built a functional solution that would succesfully access the .net environment as we need. Our connection addresses were all using localhost at that time.
var zipService:Service = new Service("http://localhost:80/project/Gateway.aspx",null,"SWFGateway.FlashLocations",null, null);
var pcZipCall:PendingCall = zipService.getStoreByZip(zip);
var pcZipCall:PendingCall = zipService.getStoreByZip(zip);
var pcZipCall.responder = new RelayResponder(_root, "getStoreByZip_Result","getStoreByZip_Status");
So as long as the address was at localhost and we were runing from localhost, it worked just fine.
However if we exchange localhost with the computer's network name, or its ip address then it breaks.
//obviously not the real ip address there
//we tried both the ip address and the name of the computer
var zipService:Service = new Service("http://1.1.1.1:80/project/Gateway.aspx",null,"SWFGateway.FlashLocations",null, null);
var pcZipCall:PendingCall = zipService.getStoreByZip(zip);
pcZipCall.responder = new RelayResponder(_root, "getStoreByZip_Result","getStoreByZip_Status");
Our IT admin people even tried setting up a web page in IIS for that computer and put the proper setups there. We could then browse to the default.aspx page in our browser, but flash remoting wouldn't work still.
We have been trying to figure this problem out now for a few days. So in a nutshel our flash remoting works only if our gateway is on localhost, and we are running on the same machine. The minute we change localhost to the ip address or computer name for that same machine, it breaks no matter where you run it.
Anybody know how to fix this?