Re: Recommended architecture for streaming over multiple sockets

On Tue, 8 Mar 2016, Ray Satiro via curl-library wrote: Do you mean you plan on leaving open ~1000 connections concurrently? Wouldn't curl_multi_wait [1] be a safer choice instead of curl_multi_fdset here? Oh right, for any solution that intends to use perhaps more than a hundred

Re: Correct package in vtls/openssl.c

On Tue, 8 Mar 2016, Gisle Vanem wrote: It does have a 'SSLeay()' prototype in include/openssl/crypto.h: /* SSLeay is a compatibility function that returns OPENSSL_VERSION_NUMBER from * base.h. */ OPENSSL_EXPORT unsigned long SSLeay(void); So I assume it's okay to use for

Re: Link between curl_easy handle and connection

On Mon, Mar 7, 2016 at 9:24 PM, Isaac Boukris wrote: > On Mon, Mar 7, 2016 at 8:01 PM, Pierre Brico > wrote: > > > > Okay, I see what you mean. You use the curl_multi API to wrap an easy > handle > > to avoid sharing connections between easy handles

Correct package in vtls/openssl.c

As mentioned previously, I've managed to build libcurl with BoringSSL okay (using MSVC-2015 + TDM-gcc). It seems the folks at Google has done a very good job with this OpenSSL fork. But I have some beefs with this combo. 'curl -V' says: curl 7.47.2-DEV (i386-pc-win32) libcurl/7.47.2-DEV

Re: Recommended architecture for streaming over multiple sockets

Hi, Thank you for your anwser Daniel. I went for the multi_interface solution, coupled with a pause when there are no data to send and unpause when there are more data. I may have several connection (~1000), with a global throughput of 800Mb/s on a localhost endpoint Currently i call

Re: Gopher [Was ""]

No I haven't looked at adding/adjusting tests, but I should. This patch was inspired by a news story about a gopher server restarting operations, so I thought I'd try to connect. My perception of what followed (as determined by writing code that I thought should work, observing results, tcpdump,

Build for QNX 6.5 on ARM Cortex A8

I want to build libcurl and curl for a TI DM3730 (ARM Cortex A8) running QNX 6.5. I see that somebody did this for an older version of curl for QNX on a 386 processor. I see hooks in the configure file for QNX, but am unsure how to build with the QNX cross-compiler on my Windows machine. Any

Re: Build for QNX 6.5 on ARM Cortex A8

On Tue, 8 Mar 2016, todd_peter...@mgtsciences.com wrote: I want to build libcurl and curl for a TI DM3730 (ARM Cortex A8) running QNX 6.5. I see that somebody did this for an older version of curl for QNX on a 386 processor. I see hooks in the configure file for QNX, but am unsure how to

Re: Recommended architecture for streaming over multiple sockets

On 3/8/2016 9:39 AM, Daniel Stenberg wrote: On Tue, 8 Mar 2016, Boutin Maël wrote: Currently i call multi_perform when there are data to be sent. How can i obtain the send status ? By performing a select on the handles ? Yes, you would call select on the file descriptors with the actions

Re: Correct package in vtls/openssl.c

Daniel Stenberg wrote: > This is simply because BoringSSL has no version number from what I understand! It does have a 'SSLeay()' prototype in include/openssl/crypto.h: /* SSLeay is a compatibility function that returns OPENSSL_VERSION_NUMBER from * base.h. */ OPENSSL_EXPORT unsigned