Hello!
>> Now let's assume that application listens on two ip:port pairs, each for
>> different kind of communication. For example, 192.168.1.1:2048 and
>> 192.168.1.1:27015. Also, let's assume that user can define on which
>> ip:port
>> one of servers should listen (another ip:port pair would be
Francois PIETTE wrote:
> A string property is very easy for the component user at runtime. A
> single line of code allows to setup all the subcomponents. And this
> ease saving/loading the configuration for the application.
>
>> As I said before creating/destroying objects on the fly depending on
A string property is very easy for the component user at runtime. A single
line of code allows to setup all the subcomponents. And this ease
saving/loading the configuration for the application.
As I said before creating/destroying objects on the fly depending on
what the user types in a strin
Since the Addr property is a string, the component could easily handle
any
special format in that field to support multiple listening IP:Port
(Interface to listen to and port to use on that interface). I think
something like "/192.168.1.1:80/0.0.0.0:81/". IPv4 or IPv6 could be used.
The component
Hello!
> Hello all,
> Since the Addr property is a string, the component could easily handle any
> special format in that field to support multiple listening IP:Port
> (Interface to listen to and port to use on that interface). I think
> something like "/192.168.1.1:80/0.0.0.0:81/". IPv4 or IPv
Francois PIETTE wrote:
> This design would not break any existing code and would ease using
> the new multiple listen easy to implement in higher level components.
It won't break existing code, but remains a hack IMO.
All event assignments and unassignments have to be kept in sync.
Also I would n
> Otherwise forcing IIS to allocate even only one IP is impossible.
It is quite possible, my public server uses IIS/7 and an ICS web
application on different IPs. There are NETSH HTTP IPLISTEN commands
that force IIS to listen only on specific IPs, or just change some
registry settings.
My app
On Fri, Nov 26, 2010 at 4:28 PM, Angus Robertson - Magenta Systems Ltd <
an...@magsys.co.uk> wrote:
> > I do not see any need for multiple listening except 0.0.0.0 and ::0
> > as I have seen none of the servers doing it.
>
> No commercial server listens on 0.0.0.0 since commercial servers all have
> I do not see any need for multiple listening except 0.0.0.0 and ::0
> as I have seen none of the servers doing it.
No commercial server listens on 0.0.0.0 since commercial servers all have
multiple IP addresses with multiple users and multiple applications, with
the exception of IIS that hogs al
Hello Francois,
Of course it will be a cool design but I do not see any need for multiple
listening except 0.0.0.0 and ::0 as I have seen none of the servers doing
it.
Regards,
SZ
On Fri, Nov 26, 2010 at 11:12 AM, Francois PIETTE wrote:
> Hello all,
>
> Since the Addr property is a string, th
Hello all,
Since the Addr property is a string, the component could easily handle any
special format in that field to support multiple listening IP:Port
(Interface to listen to and port to use on that interface). I think
something like "/192.168.1.1:80/0.0.0.0:81/". IPv4 or IPv6 could be used.
11 matches
Mail list logo
