Randall Gellens (randy@qualcomm.com)
Wed, 12 Dec 2001 21:13:55 -0700
Some comments:
I second the suggestion to use BEEP instead of HTTP.
Please use hyphens in your header attributes (e.g.,
"Notification-Protocol-Version"). Also, clarify is case is
significant (I think it shouldn't be).
What is the point of ApplicationName? Is the server going to act
differently based on the value?
You specify that all times must be in GMT (even requiring translation
from a 'Date:' header field). Using local time with a time zone
conveys more information, often useful. For example, if the event
occurred in the middle of the night versus the afternoon, local wall
time.
Your request types might be better as hierarchical codes, either
textual or numeric (like Delivery Status Notifications (DSNs)). For
example, "Account-Locked/Login-Error-Max-Exceeded" or xxx.yyy.zzz.
(Wow -- a normative reference to MIXER!)
I second the suggestion to send information on the MIME structure
instead of just Content-Disposition headers.
I'm not sure I like the idea of sending the message body. I think
that opens a potential for a lot of problems, and turns this from a
notification protocol into a third way to get local mail. At any
rate, if you are going to send the body, and you allow only part of
it to be sent, the original size needs to be included, so it is clear.
The Reject Group seems like it should use DSN codes.
The Mailbox Full Status seems like it should have a DSN code and a
human-readable text component.
This archive was generated by hypermail 2.0b3 on Thu Dec 13 2001 - 06:15:53 IST