On 6/9/01 2:55 PM, Chuck Simmons wrote:
> I have thought about this and there is no perfect solution. Server
> generated ID's are not guaranteed to be unique even for one day. It
> depends on how the ID is generated and what sort of upheavals the server
> goes through. The only guarantee you have is that a server will not
> duplicate an ID that is currently unexpired on that server.Since many
> clients generate ID's, uniqueness cannot be guaranteed anyway. I note
> that you deleted the message ID before sending the above message to test
> what I said. Your earlier message had the usual Netscape type of ID with
> <time in hex>.<32 bit pseudo random number>@<domain>. This gives a high
> probability of uniqueness.
de.all.* usenet rules prohibit Netscape type message-ids. It either has
to be a FQDN after the @ or a server generated id.
It's interesting that http://bugzilla.mozilla.org/show_bug.cgi?id=80819
has been reported by a de.all.* user :)
IMHO message-id creation should be left to the news server to avoid
dupes. Maybe best way would be if Mozilla would allow the user to
specify a FQDN via the UI or a user_pref, something like:
[] server-side m-id creation (recommended)
[] Mozilla/4 behavior
[] Use the the following FQDN for m-id:_________
(for users with their own domains)
Holger
--
Netscape 4.xx und 6.xx Tips: http://www.hmetzger.de
Mozilla 0.9.1 erschienen! http://www.mozilla.org
"And remember it's spelled Netscape but pronounced Mozilla."
(Netscape 3 Readme)
