blate
08-08-2011, 05:21 PM
Along the same lines of the in/out host interface discussion... are there plans (or is there a convenient way, at present) to have a gateway device that can be used for both inbound and outbound communications?
One irritation we presently face is having to assign two IP addresses to each application instance for each network on which it needs to perform outbound requests and receive inbound requests. I appreciate the abstraction provided by the in/out model, but there are certain practicalities to consider, as well.
Furthermore, it is often desirable for communication to and from an application to use the same IP address.
I envision an appliance called, perhaps, "GW" (gateway) that provides the functions of a firewall, NAT, and outbound default gateway. It would have a single IP address on the public grid network and would be usable in a manner similar to that of a combination of an IN and NET device.
Is this on the roadmap?
Alex
One irritation we presently face is having to assign two IP addresses to each application instance for each network on which it needs to perform outbound requests and receive inbound requests. I appreciate the abstraction provided by the in/out model, but there are certain practicalities to consider, as well.
Furthermore, it is often desirable for communication to and from an application to use the same IP address.
I envision an appliance called, perhaps, "GW" (gateway) that provides the functions of a firewall, NAT, and outbound default gateway. It would have a single IP address on the public grid network and would be usable in a manner similar to that of a combination of an IN and NET device.
Is this on the roadmap?
Alex