Configuration

Refer to "OPTIONS" in RPC::ExtDirect::Config for the list of configuration options and their default values.

Entry points

The entry point URIs are configured with the api_path, router_path, and poll_path Config options as shown in the "SYNOPSIS". These configuration options have default values that will work out of box; refer to RPC::ExtDirect::Config for details.

API definition in Perls < 5.12

If you absolutely have to use an old Perl version and Plack environment, there are two ways of dealing with this problem:

• One way is to switch to dynamic API declaration (see "DEFINING METHODS DYNAMICALLY" in RPC::ExtDirect::API) and pass the resulting API object to Plack::Middleware::ExtDirect constructor in your "app.psgi":

      use RPC::ExtDirect::API;
      use RPC::ExtDirect::Config;
      
      use My::Server::Foo;
      use My::Server::Bar;
      
      my $app = sub { ... };
      
      builder {
          my $config = RPC::ExtDirect::Config->new(
              api_path    => '/api',
              router_path => '/router',
              poll_path   => '/events',
          );
          
          my $api = RPC::ExtDirect::API->new_from_hashref(
              config   => $config,
              api_href => {
                  'My::Server::Foo' => {
                      methods => { ... },
                  },
                  'My::Server::Bar' => {
                      methods => { ... },
                  },
              },
          });
                              
          enable 'ExtDirect', api => $api;
          
          $app;
      }
      

• Another option is to make sure that all packages that provide Ext.Direct Methods - including Poll Handler methods - are loaded before Plack::Runner's "run" method is called. The easiest way to do this is to copy "plackup" script and modify it a little to "use" all relevant modules:

      use strict;
      use Plack::Runner;
      
      # Ext.Direct Action packages go here
      use My::Server::Foo;
      use My::Server::Bar;
      
      my $runner = Plack::Runner->new;
      
      $runner->parse_options(@ARGV);
      $runner->run;
      

  In fact the code above is practically the whole "plackup" script.

Environment objects

For example, "$env->http()" in CGI::ExtDirect will return the list of both environment variables and HTTP headers in upper case, while the same "$env->http()" in Plack application will return only HTTP headers as they were defined in HTTP spec.

To avoid potential problems, always find the actual header name first and then use it:

    use List::Util qw/ first /;
    
    my ($header) = first { /^Content[-_]Type$/i } $env->http();
    my $value    = $env->http($header) if $header;
    
    ...