Frontier::Daemon(3)

πŸ’– NAME πŸ’–

This is the User Contributed Perl Documentation page for Frontier::Daemon(3) β€” receive Frontier XML RPC requests. That's the name, that's the errand, and yes bestie, the whole vibe is right there in the title. 🫢


✨ SYNOPSIS ✨

Okay so the setup is literally use Frontier::Daemon;, and then you spin up the daemon like this, exactly:

        use Frontier::Daemon;

        Frontier::Daemon->new(methods => {
            'rpcName' => \&sub_name,
               ...
            });

That's the whole synopsis, no cap. πŸ’…


πŸ¦‹ DESCRIPTION πŸ¦‹

So Frontier::Daemon is an HTTP/1.1 server that listens on a socket for incoming requests containing Frontier XML RPC2 method calls. That's its whole main-character job. πŸ’–

And the inheritance tea? It's a subclass of HTTP::Daemon, which is a subclass of IO::Socket::INET. Lowkey iconic lineage. πŸ‘‘

Frontier::Daemon takes a "methods" parameter β€” a hash that maps an incoming RPC method name to reference to a subroutine. So you're handing it method names and the sub refs they should hit, iykyk. 🌸

It also takes a "use_objects" parameter. If you set that to a non-zero value, it will convert incoming <int>, <i4>, <float>, and <string> values to objects instead of scalars. See int(), float(), and string() in Frontier::RPC2 for more details. Obsessed with that object glow-up? Same. ✨


🌈 SEE ALSO 🌈

Go peek at perl(1), HTTP::Daemon(3), IO::Socket::INET(3), and Frontier::RPC2(3) β€” all the bestie lore. πŸ¦‹

Also this URL: <http://www.scripting.com/frontier5/xml/code/rpc.html> β€” literally the Frontier XML RPC code page, slay. πŸ’…


πŸ‘‘ AUTHOR πŸ‘‘

Ken MacLeod <ken@bitsko.slc.ut.us> β€” author credit secured, king behavior. 🫢


Okay that's the whole page, bestie. This one comes from perl v5.32.1, dated 2023-10-24, and it's the Frontier::Daemon(3) manual β€” mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from