|
From: Bryan L. F. <bfo...@so...> - 2002-12-06 15:23:07
|
Here's my idea on how to proceed with mixlet. Let me know of any
suggestions or problems with this.
0.5 - Where I think we stand now
0.6 - Move some things around (basically create some pacakges) and write
an ant script to compile everything
0.7 - All crypto should be internal (ie using classes from cryptix or
whatever)
0.8 - Move off of using port 25 to send mail
0.9 - Config and cleanup. Someone deploying mixlet should be able to
access a simple interface to configure it.
From there proceed with bug fixes to 1.0
For 0.8 I think we could easily supply 3 ways to send the message: a
jsp, a php page, and a cgi. All could basically take the message and
pipe it to the local mix instance.
On .9 milestone: One thing we may want to add into this is using
user-supplied keys (and stats?). I say maybe because I don't know what
all is involved in getting an applet to read local files.
I'd like to see all the mix stuff in a seperate library; Len wants this
release quickly (I think). So I'd like to make the move to a library a
goal for version 2. That would be the time to add typeIII support, I think.
Anyway, that's how I see it.
--B
|