Re: Qestions about CFHTTP: asynchronous communication mechanism
Re: Qestions about CFHTTP: asynchronous communication mechanism
- Subject: Re: Qestions about CFHTTP: asynchronous communication mechanism
- From: "Alex Guo" <email@hidden>
- Date: Wed, 8 Dec 2004 10:45:51 +0800
> Depending what you mean by "non-existing" the error may vary a little.
> In the case of the host not existing, the domain will be equal to
> kCFStreamErrorDomainNetDB and error will be one of those listed in
> netdb.h (probably EAI_NODATA). In the case the host is there but there
> is no server, domain will be equal to kCFStreamErrorDomainPOSIX and the
> error will be one of those listed in sys/errno.h (probably
> ECONNREFUSED).
>
> SSL errors work in the same manner. The domain will be equal to
> kCFStreamErrorDomainSSL and the error will be one of those listed in
> Security/SecureTransport.h. In your case, an expired certificate error
> would be errSSLCertExpired.
>
> jeremy
>
Thanks for your support !
But you know, when writing network application, we should handle many error
situations. Is there any general or graceful way can get that ?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden