>>>>The previous message was the literal and I tried to treat it the same.
>>>>Nothing happened.
>>>>
>>>>Okay, I will try to double click this one. So if it appears twice ...
>>>>
>>>>[update] Double click visually worked, but it appeared only once.
>>>
>>
>>>I never said to double click on save. This is not related to the restriction of having your message being saved.
>>
>>Assuming a fast double click, immediately at the first save time, could create such a situation as the message is being sent twice in the same second thus being processed in parallel. I'll see if that could be handled.
>>
>>So these weren't your lines, or I misunderstood.
>
>Yes, I said that but this was only to show a possible situation which would have caused that. Please, do not try it as we won't want further more situations like these. :)

No, sure I won't. I was just testing whether you could be right on your assumption, because I find it difficult to believe. Not because I don't want to believe you, but because it would attach some event stuff of which I assumed it was covered. In general that is. So YES, a second Send would send the page again, BUT, it would cancel the first, right ? There only would be time-lag for the time your server 1. already accepted the stream, put the message in the database, 2. starts to send the reply to the browser, but in between 1 and 2 I press Send again. So, it would need a twice clicking with around a second between the first and the last (depending on the response of the cable etc. of course).

So, this is the story as how I expect it to work. Now, a real (around) "double click" would be well within the second AND could be done by accident. But as I expec(ted), this would just re-send the page before you start to receive the stream. IOW, it would first get a connection again, therewith aborting the first stream.
But Michel, I'm more guessing than knowing.

Just tried to help a bit.
Peter