NAME
Net::WebSocket - WebSocket in Perl
SYNOPSIS
my $handshake = Net::WebSocket::Handshake::Client->new(
uri => $uri,
);
syswrite $inet, $handshake->create_header_text() . "\x0d\x0a" or die $!;
my $req = HTTP::Response->parse($hdrs_txt);
#XXX More is required for the handshake validation in production!
my $accept = $req->header('Sec-WebSocket-Accept');
$handshake->validate_accept_or_die($accept);
my $parser = Net::WebSocket::ParseFilehandle->new(
$inet,
$leftover_from_header_read, #can be nonempty on the client
);
my $ept = Net::WebSocket::Endpoint::Client->new(
out => $inet,
parser => $parser,
);
#Determine that $inet can be read from …
my $msg = $ept->get_next_message();
#… or, if we timeout while waiting for $inet be ready for reading:
$ept->check_heartbeat();
exit if $ept->is_closed();ALPHA QUALITY
This is a preliminary release. It is not meant for production work, but please do play with it and see how it works for you. Bug reports, especially with reproducible test cases, would be very welcome!
Breaking changes are still a possibility here, though they should be pretty minor.
DESCRIPTION
This distribution provides a set of fundamental tools for communicating via WebSocket. It is only concerned with the protocol itself; the underlying transport mechanism is up to you: it could be a file, a UNIX socket, ordinary TCP/IP, some funky tie()d object, or whatever.
Net::WebSocket also “has no opinions” about how you should do I/O or HTTP headers. As a result of this “bare-bones” approach, Net::WebSocket can likely fit your project; however, it won’t absolve you of the need to know the WebSocket protocol itself. There are some examples of how you might write complete applications (client or server) in the distribution’s demo/ directory.
Net::WebSocket is not a “quick” WebSocket solution; for that, check out Mojolicious. Net::WebSocket’s purpose is to support anything that the WebSocket protocol itself can do, as lightly as possible and without prejudice as to how you want to do it: extensions, blocking/non-blocking I/O, arbitrary HTTP headers, etc.
OVERVIEW
WebSocket is almost “two protocols for the price of one”: the HTTP-derived handshake logic, then the framing logic for the actual data exchange. The handshake portion is just an HTTP headers exchange, which CPAN’s HTTP modules already support very well, so this distribution only provides a few basic tools—the WebSocket-specific stuff, mostly—for doing the handshake. It’s enough to get you where you need to go, but not much more. You’ll need to write out some details of the handshake yourself.
Net::WebSocket handles the framing logic extensively.
Here are the main modules:
Net::WebSocket::Handshake::Server
Net::WebSocket::Handshake::Client
Logic for handshakes. These are probably most useful in tandem with modules like HTTP::Request and HTTP::Response.
Net::WebSocket::Endpoint::Server
Net::WebSocket::Endpoint::Client
The highest-level abstraction that this distribution provides. It parses input and responds to control frames and timeouts. You can use this to receive streamed (i.e., fragmented) transmissions as well.
Net::WebSocket::Streamer::Server
Net::WebSocket::Streamer::Client
Useful for sending streamed (fragmented) data rather than a full message in a single frame.
Net::WebSocket::Parser
Translate WebSocket frames out of a filehandle into useful data for your application.
Net::WebSocket::Frame::*
Useful for creating raw frames. For data frames (besides continuation), these will be your bread-and-butter. See Net::WebSocket::Frame::text for sample usage.
IMPLEMENTATION NOTES
Masking
As per the specification, client serializers “MUST” mask the data randomly, whereas server serializers “MUST NOT” do this. Net::WebSocket does this for you automatically (courtesy of Bytes::Random::Secure::Tiny), but you need to distinguish between client serializers—which mask their payloads—and server serializers, which don’t mask.
Text vs. Binary
Recall that in some languages—like JavaScript!—the difference between “text” and “binary” is much more significant than for us in Perl.
Parsed Frame Classes
Net::WebSocket tries to be as light as possible and so, when it parses out a frame, at first only a base Net::WebSocket::Frame implementation is created. An AUTOLOAD method will “upgrade” any such frame that needs the specific methods of its class.
EXTENSION SUPPORT
The WebSocket specification describes several methods of extending the protocol, all of which Net::WebSocket supports:
The three reserved bits in each frame’s header. (See Net::WebSocket::Frame.)
Additional opcodes: 3-7 and 11-15. You’ll need to subclass Net::WebSocket::Frame for this, and you will likely want to subclass Net::WebSocket::Parser. If you’re using the custom classes for streaming, then you can also subclass Net::WebSocket::Streamer. See each of those modules for more information on doing this.
THIS IS NOT WELL TESTED. Proceed with caution, and please file bug reports as needed.
Apportion part of the payload data for the extension. This you can do in your application.
TODO
Convert all plain
die()s to typed exceptions.Add tests, especially for extension support.
SEE ALSO
Mojolicious is probably CPAN’s easiest WebSocket implementation to get a server up and running. If you’re building a project from scratch, you may find this to be a better fit for you than Net::WebSocket.
Protocol::WebSocket is an older module that supports pre-standard versions of the WebSocket protocol. It’s similar to this one in that it gives you just the protocol itself, but it doesn’t give you things like automatic ping/pong/close, classes for each message type, etc.
Net::WebSocket::Server implements only server behaviors and gives you more automation than P::WS.
Net::WebSocket::EV uses XS to call a C library.
REPOSITORY
https://github.com/FGasper/p5-Net-WebSocket
AUTHOR
Felipe Gasper (FELIPE)
COPYRIGHT
Copyright 2017 by Gasper Software Consulting, LLC
LICENSE
This distribution is released under the same license as Perl.