head	1.5;
access;
symbols;
locks
	nobody:1.5; strict;
comment	@# @;


1.5
date	99.06.09.04.59.52;	author nobody;	state Exp;
branches;
next	1.4;

1.4
date	99.06.09.04.59.40;	author nobody;	state Exp;
branches;
next	1.3;

1.3
date	99.06.09.04.59.11;	author nobody;	state Exp;
branches;
next	1.2;

1.2
date	99.06.09.04.59.03;	author nobody;	state Exp;
branches;
next	1.1;

1.1
date	99.06.09.04.59.01;	author nobody;	state Exp;
branches;
next	;


desc
@null
@


1.5
log
@null
@
text
@IDependOn-Set: 1
IDependOn-Set: 189
IDependOn-Set: 191
IDependOn-Set: 192
IDependOn-Set: 193
IDependOn-Set: 2
LastModifiedSecs: 928904379
Parent: 189
SequenceNumber: 2
Title: So, why didn't you implement your own servlet API classes following the spec? 
Part: 0
Author-Set: jon@@working-dogs.com
HideAttributions: 1
LastModifiedSecs: 928904379
Type: 
Lines: 1
We thought about it but we decided to stick with Sun's to avoid platform incompatibility and to help promote following standards.
EndPart: 0
@


1.4
log
@null
@
text
@d5 1
d15 1
@


1.3
log
@null
@
text
@d6 1
a6 1
LastModifiedSecs: 928904350
d8 1
a8 1
SequenceNumber: 1
d10 7
@


1.2
log
@null
@
text
@d6 1
a6 1
LastModifiedSecs: 928904341
d8 2
a9 2
SequenceNumber: 0
Title: New Item
@


1.1
log
@null
@
text
@d3 1
@
