Re: Mojolicious::Lite and Webperl

What server would you serve your WebPerl+script from, and why can't that server directly serve your Mojolicious::Lite app?

Also, making outgoing TCP connections (like which are needed for any networked database driver) is not implemented in WebPerl (I think).

Another problem is building WebPerl with the database driver. WebPerl is a statically linked Perl and that means any module that needs a C compiler (like almost any DBD:: module) needs to be compiled into that Perl at build time.

Comment on Re: Mojolicious::Lite and Webperl Download Code

Replies are listed 'Best First'.
Re^2: Mojolicious::Lite and Webperl by haukex (Archbishop) on Apr 09, 2019 at 12:48 UTC
making outgoing TCP connections (like which are needed for any networked database driver) is not implemented in WebPerl (I think). Only partially: Emscripten supports WebSockets, and it exposes these via the C sockets API (see also), so actually Perl's sockets API is able to access it. On the server side, one would need a WebSockets proxy (e.g. websockify), assuming the server doesn't support sockets natively. This is as far as I got playing around with it on the WebPerl client side. However, the big problem is that these sockets are required to be non-blocking, and so the database driver would need to be implemented as such, which is a big ask.	[reply]
Re^2: Mojolicious::Lite and Webperl by frazap (Monk) on Apr 09, 2019 at 12:47 UTC
Thanks for replying corion The server is my organization's. It's surely Apache, and since they build mobile responsive pages, they are very restrictive on what can be made, what technology can be used. Even php is banned for the end user.	[reply]


We don't bite newbies here... much
	PerlMonks