rtGui 0.2.2 requires allow_url_fopen, this fixes it

[GoogleCodeExporter]

For rtGui 0.2.2 to work, you need to enable allow_url_fopen.
The attached patch removes that requirement by sending a message over a 
socket, instead of using file_get_contents. This includes a very very 
very basic HTTP parser. (Well, ok, actually I just skip over the header, 
hoping to find a XMLRPC message there...)

Original issue reported on code.google.com by dschridde@gmail.com on 17 Jan 2008 at 8:08

Attachments:

• no_allow_url_fopen.patch

[GoogleCodeExporter]

I like it - simpler on requirements.

Will be included in next version.

Original comment by lemonbe...@gmail.com on 17 Jan 2008 at 8:33

• Changed state: Accepted

[GoogleCodeExporter]

You probably need to enhance it a bit, for example to check for the return code 
(eg. abort if not 200).

Original comment by dschridde@gmail.com on 17 Jan 2008 at 10:22

[GoogleCodeExporter]

using cURL instead of f* calls is always an option.

Original comment by user00...@gmail.com on 19 Jan 2008 at 11:03

[GoogleCodeExporter]

I have no cURL installed, so I needed this...

Original comment by dschridde@gmail.com on 19 Jan 2008 at 11:11

[GoogleCodeExporter]

"Accepted", but 0.2.3 seems to be missing this patch...

Original comment by dschridde@gmail.com on 6 Mar 2008 at 2:20

[GoogleCodeExporter]

Yeah sorry - I completely forgot to include this in 0.2.3 (!)

Will make sure its in next version...

Original comment by lemonbe...@gmail.com on 6 Mar 2008 at 2:59

[GoogleCodeExporter]

In my opinion, there should be a few more options: fopen, cURL and fsockopen

I modified my local rtGui to use cURL (if available) over fopen, I guess I could
improve that a bit and submit a patch...

Original comment by user00...@gmail.com on 10 Nov 2008 at 5:12

[GoogleCodeExporter]

Original comment by lemonbe...@gmail.com on 5 Dec 2008 at 10:33

• Changed state: WontFix