I'm reading through the protocol doc; here are my running comments:
* Section numbers would make it much easier to reference parts
of the spec
* You're mixing protocol information and perl API information
in the same document, and even within the same section. That
means that the first time my PHP (or Java, ASP, etc. client
has trouble, I still need to look at the perl source to see
what you *really* do.
* <pre> tags around the code examples would make it easier to
read the examples.
* is the 64-char limit on strings defined by the protocol, or
just a limitation of the perl client?
* BNF (or regex's) of acceptable input for fields would be
helpful
* <META NAME="Generator" CONTENT="Microsoft Word 97"> -- This
may be why the major section heading are actually *smaller*
than the minor headings in my brower (NS4.51). Makes it
difficult to follow the flow.
I still haven't fully digested the actual protocol itself, but I
don't have any objections so far.
-mike
--
"If I should take a notion to jump into the ocean
Tain't nobody's bizness if I do"
-- Billie Holiday
GnuPG key available at http://devel.duluoz.net/pubkey.asc
Key ID = 1024D/9A256AE5 1999-11-13 Mike Glover <[EMAIL PROTECTED]>
Key fingerprint = EF6E 8BCB 4810 E98C F0FD 4596 367A 32B7 9A25 6AE5
