| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
| |
now. By gzip'ing them we can get them down to reasonable sizes.
Check in the compressed versions, remove the uncompressed versions,
add a README, and remove the old intermediate files.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
printers.
Addition of ipc7.ppt slides for presentation at the conference -
unfortunately, preliminary, i will be finishing them on friday...
|
| |
|
|
|
|
|
|
| |
too the opportunity to polish some things i was hoping to polish.
(Wish i had more time to flesh out exactly what the versatility brings
us - ease of implementing new things like mail/news gateway, cascading
lists, spam protection, accommodating emerging maillist standards,
........)
|
| |
|
|
| |
conference requirements, as well as grammatical improvements.
|
| |
|
|
|
|
|
|
| |
block-structure diagram from the Usenix paper - since it's such a nice
diagram, particularly giving a decent sense of the context for the
MailList object - but i only included a few sentences giving a very
rough overview of the structure, covering only the MailList instance
in the rest.
|
| |
|
|
| |
tweaking, am about to work on the word rendering of this.
|
| |
|
|
|
|
|
| |
haze, barely recognizing right from write from wrong and done with all
productive endeavors, until tomorrow. Maybe.
:-)
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
capitalizations). Some minor typos and other language rewrites, again
mostly minor.
Two major questions, both marked with XXX's. The first sentence in "A
Selective Tour" was completely unparseable to me. Ken could you
please rewrite? Also I rewrote the last paragraph before the
conclusion (static typing). I don't know if its any better, please
proof read.
Also note there's a slight problem with the driver excerpt, see my
recent checkin. HOwever I don't think the draft needs to change since
it's "just an excerpt".
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1) Fill in and/or fix the static typing discussion. I need your views
and your verbage - i'm in bad shape today, myself, and i didn't
have a good handle on this discussion in the first place.
2) John protested that i introduced some new ideas in the conclusion,
suggesting it's not a good idea to do that. I agree, and totally
toned down the stuff about Python's readability. (Gad, i'm so
drawn to spew about that.) My question is, is there other stuff
that needs attention?
Added a section about what mailman *is*, at the top of the
introduction. I almost overlooked this - i'm assuming it makes
sense (but i'm in bad shape today - guys, whatever sanity checking and
rectification you can provide today would be appreciated, we need to
get this done in a few hours, and i've run out of steam.)
Assembled some references - if one of you has time and knowledge about
formatting them, i'd appreciate help with that.
Incorporated two of the diagrams - user-ui.jpg and admin-ui.jpg.
Where should the structure diagram go, if it's going to go in?
Did a spell check.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
barry's arch.txt. I've also taken my first complete pass through the
document, refining the stuff i already had there (and adding, for
example, a fragment from the driver script, exhibiting the handy dandy
logging setup).
I've addressed some of barry's written comments and suggestions,
including applying some of the traditional capaitalization i tend to
ignore, and changing "maillist" to "mailing list" when referring to
the social entity - "MailList" refers to the programming class and
instance entities.
As for your "conventional protocols" question, barry - my
understanding is that conventions *are* agreements - explicit or not.
I think this is a good term, but lets scrutinize further.
|
| |
|
|
|
| |
architecture sketch. And we need to consider the title of the thing -
suggestions?
|
| |
|
|
| |
notes based on Ken's email and conversations.
|
| | |
|
| | |
|
| |
|
