May updates

In case you use some of the following modules you might be interested in reading what happened to them: App::TLSMe, Fliggy, Protocol::WebSocket, Plack::Middleware::SocketIO, MojoX::Validator, Protocol::XMLRPC.

  • App::TLSme is now on CPAN.

    App::TLSMe is an AnyEvent TLS/SSL tunnel that transparently proxies encrypted requests to the non-SSL applications via INET or UNIX sockets.

  • Fliggy is now on CPAN too.

    Fliggy is Twiggy with inlined Flash Policy server that eliminates the need of running a separate service on 843 port as root.

  • Protocol::WebSocket has an API change.

    Due to internal UTF-8 encoding/decoding sometimes when you don't need Perl strings and want to get just raw bytes you'd have to encode/decode manually and introduce unneedable overhead. Now you can get Perl string and raw UTF-8 decoded data separately by using specific methods. In Protocol::WebSocket::Frame to_string now returns Perl strings instead of bytes and to_bytes does the opposite. next left without a change and returns Perl strings as is did, but a new method next_bytes returns raw UTF-8 data.

  • Plack::Middleware::SocketIO is now considered deprecated in favor of

    Middlewares are not suitable for the end-point applications. Because of this PocketIO is now built like Plack::App::File. From now on you can just mount SocketIO application as any other Plack application.

    mount '/' => PocketIO->new(handler => sub { ... });

    PocketIO is already ahead of Plack::Middleware::SocketIO. In particular, various UTF-8 related bugs are fixed and connections are correctly closed.

  • MojoX::Validator is now Input::Validator.

    Since I wanted to use MojoX::Validator in Plack applications I've got rid of Mojolicious dependency, but not from MojoX::Validator functionality. The new Input::Validator is just the same thing with the same interface but CPAN friendly.

  • Protocol::XMLRPC is refactored.

    Protocol::XMLRPC is a XML::LibXML based XMLRPC message parser/builder. Now it has an improved automatic type guessing similar to JSON.


Hey! The above document had some coding errors, which are explained below:

  • Around line 11:

    =over without closing =back


blog comments powered by Disqus