W3C home > Mailing lists > Public > public-xg-webid@w3.org > December 2011

RE: neither FCNS nor FOAFSSL can read a new foaf card (hosted in Azure). RDFa validators at W3C and RDFachecker say its fine...

From: Peter Williams <home_pw@msn.com>
Date: Thu, 29 Dec 2011 13:54:27 -0800
Message-ID: <SNT143-W437E38E018716EC98E1F7392AD0@phx.gbl>
To: <kidehen@openlinksw.com>, "public-xg-webid@w3.org" <public-xg-webid@w3.org>

ok. Ill back off the file publication project. Ive deleted the azure http and https endpoints (to save cash). it was not a waste of time. Im much more familiar now with the latest Azure tool chain, SSL endpoints, uploading certs/chains for endpoints, , hosting blobs with TTL data in cloud blob storage, using DNS to CNAME the webid domain authority, running VPN tunnels to the cloud so the blob's cname'd http endpoints can be securely proxied by https endpoints, etc. This is all part of "commercialization". This is what IT folks do, every day.  ill go back to trying to build a __non__-native SSL library and have it listen. Lets see if that gmx.de project for SSL in user mode really works....   		 	   		  
Received on Thursday, 29 December 2011 21:55:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 29 December 2011 21:55:12 GMT