Re: [Mojolicious] Undefined address for Socket::pack_sockaddr_in

2019-12-10 Thread Veesh Goldman
can you show the command you used to start the server? On Wed, Dec 11, 2019 at 12:08 AM Pavel Serikov wrote: > I got a strange error when make GET request to Mojo server using curl: > > Undefined address for Socket::pack_sockaddr_in at >> /usr/lib/perl5/core_perl/Socket.pm line 851. >> > > Same

[Mojolicious] Undefined address for Socket::pack_sockaddr_in

2019-12-10 Thread Pavel Serikov
I got a strange error when make GET request to Mojo server using curl: Undefined address for Socket::pack_sockaddr_in at > /usr/lib/perl5/core_perl/Socket.pm line 851. > Same error I got when running server under morbo and under daemon mode. What's wrong? Notice: mojo server is running in

Re: [Mojolicious] libcurl via Mojolicious

2019-12-10 Thread Felipe Gasper
> Le 10 déc. 2019 à 14:08, Sebastian Riedel a écrit : > >>> Another big disadvantage is that it doesn't use Mojo::Promise. I don't >>> think it will attract too many Mojo users without. >> >> The latest version does, actually. > > Ah, nice. Then you can simplify your example too. > >

Re: [Mojolicious] libcurl via Mojolicious

2019-12-10 Thread Sebastian Riedel
> > Another big disadvantage is that it doesn't use Mojo::Promise. I don't > > think it will attract too many Mojo users without. > > The latest version does, actually. Ah, nice. Then you can simplify your example too. my $promiser = Net::Curl::Promiser::Mojo->new(); my $handle =

Re: [Mojolicious] libcurl via Mojolicious

2019-12-10 Thread Felipe Gasper
> Le 10 déc. 2019 à 13:57, sri a écrit : > > The disadvantage is that you’ll need to use Net::Curl::Easy, which > isn’t a very Perlish interface. HTTP::AnyUA’s backend for same demonstrates > how to “tame the beast”, though, and Net::Curl’s own documentation is quite > helpful

Re: [Mojolicious] libcurl via Mojolicious

2019-12-10 Thread sri
> > The disadvantage is that you’ll need to use Net::Curl::Easy, which > isn’t a very Perlish interface. HTTP::AnyUA’s backend for same demonstrates > how to “tame the beast”, though, and Net::Curl’s own documentation is quite > helpful (IMO), so there’s at least copious prior art to

Re: [Mojolicious] libcurl via Mojolicious

2019-12-10 Thread Felipe Gasper
Hi Stefan, The primary advantage I see is that whatever libcurl features that Net::Curl exposes are now readily usable within Mojo. So libcurl’s http/2 support, for example, should be usable, as would non-HTTP protocols that libcurl supports like FTP, IMAP, etc. (Possibly even the

Re: [Mojolicious] libcurl via Mojolicious

2019-12-10 Thread Stefan Adams
Hi, Felipe! Thanks for sharing this! What advantages does integrating with libcurl have over using Mojo::UserAgent? On Tue, Dec 10, 2019, 8:41 AM Felipe Gasper wrote: > Hi all, > > I’ve got a library called Net::Curl::Promiser that does the “dirty-work” > of interfacing between different event

[Mojolicious] libcurl via Mojolicious

2019-12-10 Thread Felipe Gasper
Hi all, I’ve got a library called Net::Curl::Promiser that does the “dirty-work” of interfacing between different event loops and Net::Curl::Multi. I recently added a Mojo::IOLoop backend, so it should now be possible to integrate libcurl seamlessly into Mojolicious via