W: AW: Deploying the client
thanks sebastian,
as i see, it's the same in .NET.
> ahhh thats your problem. In the documentation they say, that you have
> to
which documentation? i have only that one which comes with the distribution.
klaus
Am Dienstag, 17. Dezember 2002 10:08 schrieb
thanks sebastian,
as i see, it's the same in .NET.
> ahhh thats your problem. In the documentation they say, that you have to
which documentation? i have only that one which comes with the distribution.
klaus
Am Dienstag, 17. Dezember 2002 10:08 schrieb
[EMAIL PROTECTED]:
> Hi Klaus,
>
> ahhh
02 10:02
An: [EMAIL PROTECTED]
Betreff: AW: AW: AW: AW: AW: Deploying the client
Hi,
yes, but with scope as "session" i get _also_ a new session object each time
i request a method if i don't set maintainsession to true at client-code
- thats why i'm irritated.
(with scope as
Hi,
yes, but with scope as "session" i get _also_ a new session object each
time i request a method if i don't set maintainsession to true at client-code
- thats why i'm irritated.
(with scope as "application" it works as expectet _without_ do anything
at client-side - same object for each reques
CTED]]
Gesendet: Dienstag, 17. Dezember 2002 09:11
An: [EMAIL PROTECTED]
Betreff: AW: AW: AW: AW: Deploying the client
Hi Sebastian,
> Why do you think that something gows wrong on server side? If you
> deployed
yes, it works fine if i deploy the service with
_and_ set maintainsession to t
Hi Sebastian,
> Why do you think that something gows wrong on server side? If you deployed
yes, it works fine if i deploy the service with
_and_ set maintainsession to true in the client code.
but imho, i expected to do _nothing_ at client side to get
sessions working if i deployed with sess
To Barry,
you mean the AW in the subject? this is the German Re. Just showing that its
an answer. Re stands for Reply AW stands for Antwort.
To Klaus,
Why do you think that something gows wrong on server side? If you deployed
your server with that line and you set the maintainsession to true, th
