specific 'windows integration' code.
Thanks
Adam Langley
From: castle-project-users@googlegroups.com
[mailto:castle-project-users@googlegroups.com] On Behalf Of Krzysztof Kozmic
Sent: Tuesday, 19 April 2011 9:39 a.m.
To: castle-project-users@googlegroups.com
Subject: Re: New WCF Facility Lifestyle
I
.
To: castle-project-users@googlegroups.com
Subject: Re: New WCF Facility Lifestyle
I may still be missing the whole picture but
OperationContext oc = OperationContext.Current;
ServiceSecurityContext ssc = oc.ServiceSecurityContext;
string client = ssc.PrimaryIdentity.Name;
This will get you the name
[mailto:castle-project-users@googlegroups.com] On Behalf Of Krzysztof Kozmic
Sent: Sunday, 17 April 2011 9:24 p.m.
To: castle-project-users@googlegroups.com
Subject: Re: New WCF Facility Lifestyle
Sorry about the delay.
If all you need is authentication information isn't this available from
printing this email!
-Original Message-
From: castle-project-users@googlegroups.com
[mailto:castle-project-users@googlegroups.com] On Behalf Of Krzysztof Kozmic
Sent: Thursday, 14 April 2011 9:38 a.m.
To: castle-project-users@googlegroups.com
Subject: Re: New WCF Facility Lifestyle
Adam
@googlegroups.com
[mailto:castle-project-users@googlegroups.com] On Behalf Of Krzysztof Kozmic
Sent: Sunday, 17 April 2011 9:24 p.m.
To: castle-project-users@googlegroups.com
Subject: Re: New WCF Facility Lifestyle
Sorry about the delay.
If all you need is authentication information isn't
Adam,
the way I saw it done usually, in multitenant applications is to have
the component registered for each tenant and use IHandlerSelector to
manage returning the right one.
Say you're using NHibernate and you have different databases for each
tenant and each database has it's own
-project-users@googlegroups.com
Subject: Re: New WCF Facility Lifestyle
Adam,
the way I saw it done usually, in multitenant applications is to have
the component registered for each tenant and use IHandlerSelector to
manage returning the right one.
Say you're using NHibernate and you have
Dear group,
I have a requirement where-by I will have a Windows Service (running as
System) that publishes a component on net.pipe (for use by the local
machine only), but it must service multiple users logged on to the same
machine simultaneously.
It must create a 'singleton' instance per
