realbasic-nug
[Top] [All Lists]

Re: Synchronous HTTP requests

To: REALbasic NUG <realbasic-nug at lists dot realsoftware dot com>
Subject: Re: Synchronous HTTP requests
From: Norman Palardy <palardyn at shaw dot ca>
Date: Thu, 30 Dec 2004 18:18:14 -0700
Delivered-to: realbasic-nug at lists dot realsoftware dot com
References: <3C70D4ED-5ABA-11D9-951A-000A95A9544A at shaw dot ca> <C11F6B2C-5ABA-11D9-8A9B-000393101B4A at mobleybros dot com> <EE1D8809-5ABD-11D9-8A9B-000393101B4A at mobleybros dot com> <57D06E78-5AC3-11D9-951A-000A95A9544A at shaw dot ca> <FAB83948-5AC5-11D9-8A9B-000393101B4A at mobleybros dot com>

On Dec 30, 2004, at 5:50 PM, Phil Mobley wrote:

On Dec 30, 2004, at 4:31 PM, Norman Palardy wrote:

Actually, the docs say that HTTP status is passed along with the contents in the "PageReceived" event. 404 is used in the example, so you just need to subclass and handle you missing link there.

IF you use the asynchronous mechanisms this is true .... at least thats how I read it and a quick test indicates that this is the case

(Waiting for Aaron to chime in...)

I have an app which uses HTTPSocket quite extensively. I gave up on synchronous because my app would "hang" when the user quits until the HTTPSocket Timeout period expires. And since this app is all about polling web pages, the sockets are constantly firing. There were just too many disadvantages for synchronous mode.

Sorry, I can't be more help.  =(

This ones less active than that ... and the timeout I can set long enough to be useful but short enough ...

I'm going to play with it I guess

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>

<Prev in Thread] Current Thread [Next in Thread>