11 results (0.029 seconds)
Jason McManus
POE::Component::Client::opentick - A POE component for working with opentick.com's market data feeds.
POE::Component::Client::opentick::Constants - Constants for the opentick POE Component.
POE::Component::Client::opentick::Error - Error handling routines for opentick client.
POE::Component::Client::opentick::FAQ - The official FAQ for POE::Component::Client::opentick.
POE::Component::Client::opentick::OTClient - An opentick.com otFeed-compatible interface for the POE opentick client.
POE::Component::Client::opentick::Output - Diagnostic message output class.
POE::Component::Client::opentick::Protocol - Protocol handling routines for opentick client.
POE::Component::Client::opentick::ProtocolMsg - Individual protocol message handling.
POE::Component::Client::opentick::Record - Encapsulation for data records for the POE opentick.com component.
POE::Component::Client::opentick::Socket - Socket handling routines for the opentick POE component.
POE::Component::Client::opentick::Util - Utility routines for the opentick POE Component.
Changes for version 0.21
    • BUG: Constant.pm:OTeod() wasn't checking definedness of $data_type
    • BUG: Protocol.pm:_send_notification() did string comp. with ==
    • FIX: OTClient.pm:cancelBookStream() had extraneous crap in it.
    • FIX: Added lexical 'use warnings' throughout. (No problems were caused; I run locally with PERL5OPT=-w )
    • FIX: opentick.pm was checking a couple of unitialized variables.
    • FIX: Minor warning corrections in Socket.pm, Protocol.pm
    • DOC: Clarified and unified all documentation throughout distribution.

Hosting generously
sponsored by Bytemark