> I' am new today on this list. But Today I get a new problem that a can't
fix
> with any example code find on the net.
>
> So anybody can help me to send ICMP Message 17 and get response ICMP
answer
> (18) (RFC950)
>
> I need this to get the Subnet mask from a remote machine only with IP.
Not su
Hi all,
I am new today on this list. But Today I get a new problem that a cant fix
with any example code find on the net.
So anybody can help me to send ICMP Message 17 and get response ICMP answer
(18) (RFC950)
I need this to get the Subnet mask from a remote machine only with IP.
Jon Rowlan wrote:
> I have searched the FAQ and Archives
>
> I am trying to extract just the attachments from mail messages in a
> POP3 mailbox.
Use TMimeDec to decode the message. A demo program is available in
directory ICS-Root/Delphi/Internet.
> Having tested two emails I am confused.
I have searched the FAQ and Archives
I am trying to extract just the attachments from mail messages in a POP3
mailbox.
Having tested two emails I am confused.
Both have a single attachment, one is a PDF file and appears to be quite
clearly identified with a "Disposition=attachment" indic
Hello:
I don't see anything recently in the list about MIME. What was the
subject line? In any case, perhaps you should repost.
dZ.
On Jun 28, 2006, at 05:21, Jon Rowlan wrote:
> I sent a mail a few days ago regarding intepretation of Mime mails and
> attachments.
>
> I am not
I sent a mail a few days ago regarding intepretation of Mime mails and
attachments.
I am not sure that the mail got through as I have not seen my mail
bounced on to me.
Can someone confirm whether that was the case?
Thanks,
jON
--
To unsubscribe or change your settings for TWSocket mailing lis
Now all is clear!! :-)
Thanks,
Emanuele
Francois Piette ha scritto:
>> The problem was on the receiver side. Inside DataAvailable there
>> are onerous instructions for CPU. So winsock messages
>> tend to accumulate in Message queue.
>> When new packets arrive, the receiver progressively reduce
>>
> The problem was on the receiver side. Inside DataAvailable there
> are onerous instructions for CPU. So winsock messages
> tend to accumulate in Message queue.
> When new packets arrive, the receiver progressively reduce
> TCP sliding window until 0.
That is perfectly correct and expected behavi
The problem was on the receiver side. Inside DataAvailable there are
onerous instructions for CPU. So winsock messages tend to accumulate in
Message queue.
When new packets arrive, the receiver progressively reduce TCP sliding
window until 0.
Now, with a dedicated thread that manage winsock mess
