Hi Jamie,
Thanks for your information. It's helpful for me. I am aiming a program run
on clients' computers. So this may not suitable now.
Appreciated your email. Wish you have a good day.
Sincerely,
Jed
> -----Original Message-----
> From: Jamie Mutton [mailto:
ja...@rosewood-prestbury.co.uk]
> Sent: Thursday, May 13, 2010 5:17 PM
> To: 'Jedliu';
cse...@googlegroups.com
> Cc:
meh...@gmail.com
> Subject: RE: two csExwb processes share same session and cookies
>
> It runs on vista, win 7 + windows 2003 server onwards
>
> I was working on something which was more service related and the csexwb
> component was being used as a service to extract content from pages...
>
> Its wasn't for about sharing sessions or cookies but rather having
servers
> which could run the IE components without memory or handle leaks
>
> -----Original Message-----
> From: Jedliu [mailto:
jed...@gmail.com]
> Sent: 13 May 2010 04:05
> To: 'Jamie Mutton';
cse...@googlegroups.com
> Cc:
meh...@gmail.com
> Subject: RE: two csExwb processes share same session and cookies
>
> Hi Jamie,
>
> Thanks a lot for your reply.
>
> I googled and didn't found much about WAS. And is WAS can only run in
Vista?
> Can csExwb or webbrowser programs run inside and share session and
> cookies?
> Could you please advise more information of WAS?
>
> Thanks very much!
>
> Sincerely,
> Jed
>
>
>
> > -----Original Message-----
> > From: Jamie Mutton [mailto:
ja...@rosewood-prestbury.co.uk]
> > Sent: Thursday, May 13, 2010 1:51 AM
> > To:
cse...@googlegroups.com;
jed...@gmail.com
> > Cc:
meh...@gmail.com
> > Subject: RE: two csExwb processes share same session and cookies
> >
> > I don't know if this is of use, but I dealt with the issue of memory
> > leaks etc. with the IE components by using a feature of Windows server
> > called
> WAS
> > (Windows Process Activation Service) - in effect it's like IIS but for
> your
> > services. You could then specify how frequently the process is
> > recycled
> so
> > existing requests complete, a new process is spun up for the new
> > requests and when the last of the requests on the old process finishes
> > , the
> process
> > is terminated.
> >
> > Trust this helps.
> >
> > Jamie