On 08/01/2012 02:44 PM, icorderi wrote:
> David Schmitt wrote
>> Isn't there a wildcard syntax or something like that? Hmm: Fourth hit on
>> Google:
>>
>> http://stackoverflow.com/q/10649078/4918
>>
>>> The point is to replace host name in base address with "*" symbol
>>> (wildcard). It will be
David Schmitt wrote
>
> Isn't there a wildcard syntax or something like that? Hmm: Fourth hit on
> Google:
>
> http://stackoverflow.com/q/10649078/4918
>
>> The point is to replace host name in base address with "*" symbol
>> (wildcard). It will be changed with actual host name in run time.
On 7/31/2012 5:45 PM, icorderi wrote:
Basically, when you host the wcf service on the console with a uri like
"net.tcp://localhost:8081" on a linux box the socket address is not bind to
listen on 0.0.0.0:8081 instead it listens on 127.0.0.1:8081 essentially
refusing all connections from other mac
On 01.08.2012 01:57, icorderi wrote:
@Rob Yes localhost is translated to 127.0.0.1 on hosts. But
regardless of that, if the wcf service is hosted as
net.tcp://localhost:8081 it should work as expected.
I would expect it to use localhost if localhost is specified.
An easy workaround is to chan
2012/8/1 icorderi
> @Rob
> Yes localhost is translated to 127.0.0.1 on hosts.
> But regardless of that, if the wcf service is hosted as
> net.tcp://localhost:8081 it should work as expected.
>
But in many cases you specify localhost when you specifically do want to
prevent connections from other
@Rob
Yes localhost is translated to 127.0.0.1 on hosts.
But regardless of that, if the wcf service is hosted as
net.tcp://localhost:8081 it should work as expected.
An easy workaround is to change the config to net.tcp://:8081.
I can live with that workaround although localhost should work as expe
I believe if you look up 'localhost' in your hosts file, it will
translate it to 127.0.0.1 -- if your machine has another IP address or
name, you should probably not specify localhost.
I'm not saying it's not broken, but that's the way localhost usually
translates to IP address form.
-Rob
On 07
It *should *work but it *doesn't*.
I'm facing the same issue described by hiking.
Basically, when you host the wcf service on the console with a uri like
"net.tcp://localhost:8081" on a linux box the socket address is not bind to
listen on 0.0.0.0:8081 instead it listens on 127.0.0.1:8081 essenti
Hi
This scenario should work on Mono 2.8+, yes.
Cheers,
Alex
2011/3/23 hiking :
> hi,
> i want to know if the mono works in the below situation.
> i have a server writing by wcf:
> static void Main(string[] args)
> {
> ServiceHost host = new ServiceHost(typeof(Foo));
>
hi,
i want to know if the mono works in the below situation.
i have a server writing by wcf:
static void Main(string[] args)
{
ServiceHost host = new ServiceHost(typeof(Foo));
NetTcpBinding binding = new NetTcpBinding();
binding.Security.Mode = Sec
hi,
i want to know if the mono works in the below situation.
i have a server writing by wcf:
static void Main(string[] args)
{
ServiceHost host = new ServiceHost(typeof(Foo));
NetTcpBinding binding = new NetTcpBinding();
binding.Security.Mode = Sec
11 matches
Mail list logo
