RE: A Game (Email - Kelly)

>     Kelly> Essentially, I am enhancing an existing client. I'm=0D=0A>    =
 Kelly> essentially rewriting Eudora. If I'm not mistaken there are=0D=0A> =
    Kelly> more former Eudora users than Mutt users, but I could be=0D=0A> =
    Kelly> wrong.=0D=0A>=20=0D=0A> Why does this need to be done within a c=
lient=3F  You're=20=0D=0A> restricting your market.=0D=0A=0D=0AYeah, I know=
 :-(  I admit that it's a problem.=20=0D=0A =20=0D=0A>     Kelly> It's an i=
nteresting idea, the IMAP extension. I have a bias=0D=0A>     Kelly> agains=
t web based applications because I enjoy a smooth=0D=0A>     Kelly> user in=
terface experience.=0D=0A>=20=0D=0A> IMAP isn't "web-based".  It's a specia=
lized database=20=0D=0A> protocol, like (though quite different from) LDAP.=
  The point=20=0D=0A> is that if you have a filter/scoring system that work=
s with=20=0D=0A> IMAP, any IMAP-enabled client can benefit.=0D=0A=0D=0AI kn=
ow what IMAP is. I should have said "server based" rather than "web=0D=0Aba=
sed". The problem is that the client would have to send information to=0D=0A=
this IMAP extension. The other thing is that there are not spare CPU=0D=0Ac=
ycles on the server, while there are on the client. That's one of the=0D=0A=
major reasons to make it client based from my point of view. I suppose=0D=0A=
that the client could do the computations, and send the results back to=0D=0A=
the server, but then it stops looking like IMAP...=20=0D=0A=0D=0AIn general=
, I like the idea of trying to make it MUA independent. I will=0D=0Ajust ha=
ve to think about how it could be accomplished.=0D=0A=0D=0A> I guess both o=
f these points can be refined to "why does your=20=0D=0A> idea need access =
to the client's UI=3F"=0D=0A=0D=0AHow else would you determine the "role"=3F=
 I suppose that you could set up=0D=0Adifferent fake email addresses for ea=
ch role via an IMAP interface, but=0D=0AI'm not sure how it would work. I w=
ill think=0D=0A=0D=0A-Kelly=0D=0A=0D=0A=0D=0A=0D=0A=0D=0A=0D=0AE-Mail messa=
ges may contain viruses, worms, or other malicious code. By reading the mes=
sage and opening any attachments, the recipient accepts full responsibility=
 for taking protective action against such code. Sender is not liable for a=
ny loss or damage arising from this message.=0D=0A=0D=0AThe information in =
this e-mail is confidential and may be legally privileged. It is intended s=
olely for the addressee(s). Access to this e-mail by anyone else is unautho=
rized.=0D=0A