Re: [twsocket] THttpCli...

2008-05-11 Thread zayin
Hello,

>Are you referring here to CamCollect or your own application?
 
CamCollect

I spent hours last night attempting to locate the problem. I went so far as
to cycle power on the camera, reset to defaults, and cycle power on my
computer, to no resolution.

This morning/afternoon I can not get it to fail. I had it running for 3+
hours and not one hiccup. It is running now in the background and working
flawless.

The only hardware I did not cycle power on is the router.

For Francois P., I am not calling any message pump calls, etc.. Most of my
ICS callbacks are very short and post a message. 

For now, I will keep on the motion detection path I am on and be watchful
for the error again.

Thank guys,

Mark





-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Angus Robertson - Magenta Systems Ltd
Sent: Sunday, May 11, 2008 1:19 PM
To: twsocket@elists.org
Subject: Re: [twsocket] THttpCli...

> Thanks for the link. Watching the debug window most of the time it 
> works like clock work. Sometimes I see the content length and then it 
> pauses and then indicates finished and starts again. So, there is a 
> watchdog timer but its firing is not logged.

Are you referring here to CamCollect or your own application?

CamCollect does have a download timeout to cope with a slow internet, but if
you are seeing the same problem in CamCollect as your own application, it
suggests the IP camera is at fault. 

Angus

--
To unsubscribe or change your settings for TWSocket mailing list please goto
http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] THttpCli...

2008-05-11 Thread Angus Robertson - Magenta Systems Ltd
> Thanks for the link. Watching the debug window most of the time it 
> works like clock work. Sometimes I see the content length and then it 
> pauses and
> then indicates finished and starts again. So, there is a watchdog 
> timer but its firing is not logged.

Are you referring here to CamCollect or your own application?

CamCollect does have a download timeout to cope with a slow internet, but
if you are seeing the same problem in CamCollect as your own application,
it suggests the IP camera is at fault. 

Angus

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] THttpCli...

2008-05-11 Thread zayin

Hello,

Thanks for the link. Watching the debug window most of the time it works
like clock work. Sometimes I see the content length and then it pauses and
then indicates finished and starts again. So, there is a watchdog timer but
its firing is not logged.

I set the frequency to 1 sec, the lowest, and the pause is about 5 seconds.

Ciao,

Mark




-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Angus Robertson - Magenta Systems Ltd
Sent: Sunday, May 11, 2008 8:07 AM
To: twsocket@elists.org
Subject: Re: [twsocket] THttpCli...

> I am using an THttpCli and collecting  jpegs from a video camera.
> I have found that sometimes the GetAsync fails because the complete 
> document is not sent and it always fails with the same byte count.

Try using my CamCollect application, it does exactly the same thing using
ICS V5, see if you get the same problem, it also logs the protocol: 

http://www.magsys.co.uk/camcollect/ccbeta.asp

Angus

--
To unsubscribe or change your settings for TWSocket mailing list please goto
http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] THttpCli...

2008-05-11 Thread Angus Robertson - Magenta Systems Ltd
> I am using an THttpCli and collecting  jpegs from a video camera.
> I have found that sometimes the GetAsync fails because the complete 
> document is not sent and it always fails with the same byte count.

Try using my CamCollect application, it does exactly the same thing using
ICS V5, see if you get the same problem, it also logs the protocol: 

http://www.magsys.co.uk/camcollect/ccbeta.asp

Angus

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] THttpCli...

2008-05-11 Thread Francois PIETTE
> I am using an THttpCli and collecting  jpegs from a video camera.
>
> I have found that sometimes the GetAsync fails because the complete 
> document
> is not sent and it always fails with the same byte count.
>
> I am tracking the bytes received from the DocData event.
>
> If the image is not received in X seconds I log all the information I can
> think to but I am still not able to find the cause of the problem. 
> Changing
> the timeout does not change the failure.
>
> I am not getting any exceptions. I have set up to catch BGExecption and it
> never fires.
>
> The content length various but the failure always is with the same number 
> of
> bytes received.
>
> The text that follows shows successes and failures. The line
> "Watchdog***" is the failure. The
> "RequestDone Error = 3. Status = 404" that follows is my call to Abort.

I see that each time your watchdog trigger, you have received exactly 37960 
bytes. Strange.
To know if the issue is in your program (You code or ICS code), or at the 
camera, you should use a network sniffer to capture data sent by the camera 
on the network and check if the number of bytes sent is exactly what is 
specified in the header.

If the issue is in your program, then test with HttpTst sample program 
delivered with ICS. Modify it the less possible. This would confirm that the 
bug is in the component (not likely) or in you own code.

One common cause of have data corrupted, ducplicated or incomplete, is to 
call the message pump from one of the events of the ICS component. You can't 
do that. So check if it is not the case in your application. The message 
pump can be called directly (Application.ProcessMessages, GetMessage, and 
the likes) or indirectly by displaying a modal form (including MessageBox).


--
[EMAIL PROTECTED]
The author of the freeware multi-tier middleware MidWare
The author of the freeware Internet Component Suite (ICS)
http://www.overbyte.be

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be