That's not necessarily the most secure way. We have found that even though IMAP is supposed to be a long state protocol many clients (PINE, Netscape, Balsa, M$ Outlook Express, etc) implement as connect/work/disconnect cycle. So I don't think this persistency of connection across multiple accesses is really necessary.
> -----Original Message----- > From: Ask Bjoern Hansen [mailto:[EMAIL PROTECTED]] > Sent: Saturday, June 08, 2002 5:32 PM > To: Richard Clarke > Cc: [EMAIL PROTECTED] > Subject: Re: persistent Mail::ImapClient and webmail > > > On Fri, 7 Jun 2002, Richard Clarke wrote: > > > p.s. Yes quite obviously if I have 100 children then I'll > be connected to > > the IMAP server 100 times per user, hence possibly the need > to have a either > > a dedicated daemon connected to the IMAP server once or > some successfuly way > > of sharing IMAP objects between children. > > the trivial way would be to have the mod_perl processes login (once > each) as some kind of super user and then access the folders as > "[username]/INBOX" etc. > > > - ask > > -- > ask bjoern hansen, http://ask.netcetera.dk/ !try; do(); > >
