[mashup-dev] WSAS Prominent Network Interface Re-direction inherited in the Mashup Server

[Tyrell Perera]

Hi all,

I have noticed that since the Mashup Server is based on WSAS, it
redirects calls to the loopback address, to the prominent interface IP.
In other words, a user can not use 127.0.0.1 or localhost to connect to
the Mashup server.

Since we are planning on allowing the users to install the server
locally in their individual machines, is this a vice approach?

Consider a scenario where a user logs to a corporate network using DHCP.
This means his machine will have a dynamically allocated IP while on the
network and 'no IP' while disconnected. If this user tries to work on
the Mashup server while he is disconnected (i.e.; at home), he might not
be able to do so.

I'm sure there is a valid reason behind the usage of this approach in
WSAS. But is it absolutely necessary on the Mashup server?

Thanks,

Tyrell


-- 
Tyrell Perera
Senior Software Engineer; WSO2, Inc.; http://www.wso2.com/
email: tyrell at wso2.com; cell: +94 77 302 2505

"Oxygenating the Web Service Platform."