Hi
It’s created on the web side, every now and again it double posts, I’ve
had it happen, if a user is quick enough it may be deleted. If the
gateway is polling, then it can be hit and miss.
On 10/04/2011 05:49 AM, malcolmlewis wrote:
> It’s created on the web side, every now and again it double posts, I’ve
> had it happen, if a user is quick enough it may be deleted. If the
> gateway is polling, then it can be hit and miss.
i’ve seen double posts from time to time…i think it can happen like
this:
web user presses ‘Send’ (post, or whatever) just before the gateway
runs–and passes the post to the nntp server
then, web user clicks edit and makes changes (or not)
next time the gateway runs it sees the changed post as one it has not
passed to the nntp server, so it does…
there are other situations where a single post on the nntp side is not
exactly as it appears on the web side…i’ve seen that when a mod edits
or removes a post, the original remains unchanged on the nntp side…
–
DD
openSUSE®, the “German Automobiles” of operating systems
On 2011-10-04 10:08, DenverD wrote:
> On 10/04/2011 05:49 AM, malcolmlewis wrote:
>> It’s created on the web side, every now and again it double posts, I’ve
>> had it happen, if a user is quick enough it may be deleted. If the
>> gateway is polling, then it can be hit and miss.
Dunno.
> i’ve seen double posts from time to time…i think it can happen like this:
>
> - web user presses ‘Send’ (post, or whatever) just before the gateway
> runs–and passes the post to the nntp server
>
> - then, web user clicks edit and makes changes (or not)
>
> - next time the gateway runs it sees the changed post as one it has not
> passed to the nntp server, so it does…
Yes, I understand that, but in that case the two posts would have different
dates, and they have the same date to the second. The path header is also
exactly the same. Ditto for X-Trace. Only the Message-ID is different.
The Message-ID can be generated locally by leafnode, but in that case it
would have the name of my machine on it. So it is one generated at the
Novell server, no doubt about that.
I think the double is generated in the gateway or in the nntp server, not
the web side. At least this one.
> there are other situations where a single post on the nntp side is not
> exactly as it appears on the web side…i’ve seen that when a mod edits or
> removes a post, the original remains unchanged on the nntp side…
Yes, like spam. It is very confusing.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
> they have the same date to the second. …
> I think the double is generated in the gateway or
> in the nntp server, not the web side. At least this one.
agree…
–
DD
openSUSE®, the “German Automobiles” of operating systems
On Tue, 04 Oct 2011 09:33:06 +0000, Carlos E. R. wrote:
> Yes, I understand that, but in that case the two posts would have
> different dates, and they have the same date to the second. The path
> header is also exactly the same. Ditto for X-Trace. Only the Message-ID
> is different.
The message timestamp for posts that come from the webside is the time
the message came through the gateway. Multiple messages come through in
a given second, so it’s not surprising that that field (and likely x-
trace as well).
It seems to be a timing issue and nothing more. It’s not frequent, so
it hasn’t gotten a lot of attention and isn’t likely to.