On Apr 7, 2006, at 2:25 AM, Guyren Howe wrote:
On Apr 7, 2006, at 1:56 AM, Guyren Howe wrote:
I create a HTTPSocket subclass, I ask it to get an address, it
works fine.
I change its super to HTTPSecureSocket, I add the following
constructor:
Me.Secure = False
Super.Constructor
and I ask it to get the same address, it eventually fails with
a 103 error (which the TCPSocket docs say is a DNS failure).
I can't find a bug report on this. Anyone have any advice?
Oh, and this is 2K6r1 on OS X.
On Apr 7, 2006, at 12:35 PM, Jason Essington wrote:
Maybe a little more information would be useful ...
How are you using this socket? Is it instantiated in code, or is it
a control on a window?
Could you post the code for your socket subclass? that would help
also.
As I've said. I use HTTPSecureSocket as a subclass in our
applications and it works just fine.
This is super-simple to reproduce:
Create new project. Add class. Set its super to HTTPSecureSocket.
Give it a DoIt Method:
Me.Get "http://foo.com";.
Give it a PageReceived handler:
MsgBox "Works"
Give it a Error handler:
break
In App.Open, do:
Dim x As New Class1
x.DoIt
Run. After five seconds or so, you'll get dropped into the Error
handler, showing a 103 error.
Now, change the Super of Class1 to HTTPSocket, and run again. Success!
Guyren G Howe
guyren-at-relevantlogic.com
http://relevantlogic.com
REALbasic, PHP, Python programming
PostgreSQL, MySQL database design and consulting
Technical writing and training
_______________________________________________
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>
