view release on metacpan or search on metacpan
lib/CGI/Wiki/Plugin/Locator/Grid.pm view on Meta::CPAN
unit => "kilometres" );
Defaults to metres if C<unit> is not supplied or is not recognised.
Recognised units at the moment: C<metres>, C<kilometres>.
Returns C<undef> if one of the endpoints does not exist, or does not
have both co-ordinates defined. The C<node> specification of an
endpoint overrides the x/y co-ords if both specified (but don't do
that).
B<Note:> Works to the nearest metre. Well, actually, calls C<int> and
rounds down, but if anyone cares about that they can send a patch.
view release on metacpan or search on metacpan
lib/CGI/Wiki/Plugin/Locator/UK.pm view on Meta::CPAN
unit => "metres" );
Defaults to kilometres if C<unit> is not supplied or is not recognised.
Recognised units at the moment: C<metres>, C<kilometres>.
Returns C<undef> if one of the endpoints does not exist, or does not
have both co-ordinates defined. The C<node> specification of an
endpoint overrides the x/y co-ords if both specified (but don't do
that).
B<Note:> Works to the nearest metre. Well, actually, calls C<int> and
rounds down, but if anyone cares about that they can send a patch.
view release on metacpan or search on metacpan
lib/CGI/Wiki/Plugin/Locator/UTM.pm view on Meta::CPAN
unit => "metres" );
Defaults to kilometres if C<unit> is not supplied or is not recognised.
Recognised units at the moment: C<metres>, C<kilometres>.
Returns C<undef> if one of the endpoints does not exist, or does not
have both co-ordinates defined.
B<Note:> Works to the nearest metre. Well, actually, calls C<int> and
rounds down, but if anyone cares about that they can send a patch.
view release on metacpan or search on metacpan
lib/CPAN/Common/Index/MetaDB.pm view on Meta::CPAN
use CPAN::Meta::YAML;
use HTTP::Tiny;
#pod =attr uri
#pod
#pod A URI for the endpoint of a CPAN MetaDB server. The
#pod default is L<http://cpanmetadb.plackperl.org/v1.0/>.
#pod
#pod =cut
sub BUILD {
view release on metacpan or search on metacpan
t/unpacked/GraphViz/lib/GraphViz.pm view on Meta::CPAN
sets the arrow direction. Can be one of: 'forward', 'back', 'both', 'none'
=item tailclip, headclip
when set to false disables endpoint shape clipping
=item arrowhead, arrowtail
sets the type for the arrow head or tail. Can be one of: 'none',
'normal', 'inv', 'dot', 'odot', 'invdot', 'invodot.'
view release on metacpan or search on metacpan
t/distrolist.t view on Meta::CPAN
for ( '0.01', '0.02') {
my $path = sprintf $distro_path_tmpl, $_;
# uris
my $uri = $fakepan->endpoint;
$uri->path($path);
push @fake_distro_uris, $uri->as_string;
# paths
my $source = file($fakepan->dest, $path)->stringify;
view release on metacpan or search on metacpan
t/distribution.t view on Meta::CPAN
$fakepan->$_ for qw(_update_author_checksums write_package_index
write_author_index write_modlist_index write_perms_index);
my $distro_path = 'authors/id/L/LO/LOCAL/Foo-Bar-0.01.tar.gz';
my $distro_uri = $fakepan->endpoint;
$distro_uri->path($distro_path);
$distro_uri = $distro_uri->as_string;
$distro{uri} = $distribution_class->new( uri => $distro_uri );
view release on metacpan or search on metacpan
is_deeply(
$req->as_string_hash,
{
Foo => '> 1, <= 2',
},
"we can exclude an endpoint",
);
}
{
my $req = CPAN::Meta::Requirements->new;
view release on metacpan or search on metacpan
[Fixed]
- Upgraded Mojolicious::Plugin::OpenAPI to 1.13 to fix deprecations
due to Mojo::File
- Fixed API website links to point to /v3 API endpointes
- Fixed test report post to use new schema with auto-serialization.
This makes our database more consistent.
0.007 2017-05-12 10:35:47+02:00 Europe/Paris
view release on metacpan or search on metacpan
t/data/zx48.asm view on Meta::CPAN
; continue if a match of all eight bytes was found
POP BC ; discard the
POP BC ; saved
POP BC ; pointers
LD A,$80 ; the endpoint of character set
SUB B ; subtract the counter
; to give the code 32-127
LD BC,$0001 ; make one space in workspace.
RST 30H ; BC-SPACES creates the space sliding
view release on metacpan or search on metacpan
t/embedded_style_block.t view on Meta::CPAN
eval {
$inliner->fetch_file({ url => $test_url });
};
## conditional test plan based on whether or not the endpoint can be reached - frequently can't by cpan testers
plan $@ ? (skip_all => 'Connectivity for endpoint required for test cannot be established') : (tests => 2);
my $inlined = $inliner->inlinify();
ok($inlined eq $correct_result, 'result was correct');
view release on metacpan or search on metacpan
t/33_cqp_errors.t view on Meta::CPAN
for my $R (-1, -2, -42) { # T6–T8
syntax_error("A = 'the' []{$R} 'elephant'", "negative repetition count {$R}", qr/non-negative/i);
}
for my $R (-1, -2) { # T9–T10
syntax_error("A = 'the' []{0,$R} 'elephant'", "invalid endpoint of repetition range {0,$R}", qr/non-negative/i);
}
for my $R (1, 2, 3) { # T11–T13
my $R1 = $R - 1;
syntax_error("A = 'the' []{$R,$R1} 'elephant'", "invalid repetition range {$R,$R1}", qr/invalid.*range/i);
view release on metacpan or search on metacpan
examples/EVStest.pl view on Meta::CPAN
#
# ApplicationService is a utility classs that encapsulates webservice invocation to caCORE server.
# ApplicationService object follows the Singleton pattern, in that each program will ONLY contain one instance
# of such class.
# The URL being passed to the intance method is the service endpoint of the caCORE webservice.
# If no such URL is provided in the program, it will default to the caCORE production server, "http://cabio.nci.nih.gov/cacore30/ws/caCOREService"
#
my $appsvc = CaCORE::ApplicationService->instance("http://cabio.nci.nih.gov/cacore32/ws/caCOREService");
my $num2 = 0;
view release on metacpan or search on metacpan
lib/Cache/Elasticache/Memcache.pm view on Meta::CPAN
=head1 SYNOPSIS
use Cache::Elasticache::Memcache;
my $memd = new Cache::Elasticache::Memcache->new({
config_endpoint => 'foo.bar',
update_period => 180,
# All other options are passed on to Cache::Memcached::Fast
...
});
# Will update the server list from the configuration endpoint
$memd->updateServers();
# Will update the serverlist from the configuration endpoint if the time since
# the last time the server list was checked is greater than the update period
# specified when the $memd object was created.
$memd->checkServers();
# Class method to retrieve a server list from a configuration endpoint.
Cache::Elasticache::Memcache->getServersFromEndpoint('foo.bar');
# All other supported methods are handled by Cache::Memcached::Fast
# N.B. This library is currently under development
=head1 DESCRIPTION
A wrapper for L<Cache::Memacached::Fast> with support for AWS's auto reconfiguration mechanism. It makes use of an AWS elasticache memcached cluster's configuration endpoint to discover the memcache servers in the cluster and periodically check the c...
=head1 UNDER DEVELOPMENT DISCALIMER
N.B. This module is still under development. It should work, but things may change under the hood. I plan to imporove the resiliance with better timeout handling of communication when updating the server list. I'm toying with the idea of making the s...
view release on metacpan or search on metacpan
lib/Cache/RamDisk.pm view on Meta::CPAN
1. Message queues are extremely fast, but extremely limited too.
2. Shared memory is perhaps even faster, but it came out for me to be an at least hairy problem
trying to store several references all in one segment.
3. Sockets are reliable, but require a second communication endpoint and yet another server process.
But a file is a file is a file.
The package collects as much ramdisks to a bundle as possible and necessary to hold the required user space,
depending on the respective parameters under which the system's individual kernel had been compiled.
view release on metacpan or search on metacpan
lib/Calendar/Japanese/Acme/Syukujitsu.pm view on Meta::CPAN
sub new {
args
my $class,
my $cachefile => {optional => 1},
my $endpoint => {optional => 1};
my $data;
if ($cachefile) {
$data = read_file($cachefile);
} else {
$endpoint = $endpoint || $DEFAULT_ENDPOINT;
$data = Furl->new()->get($endpoint)->content;
}
Encode::from_to($data, 'sjis', 'utf-8');
my $syukujitsus = {};
for my $line (split /\n/, $data) {
view release on metacpan or search on metacpan
t/catalyst-action-rest-action-dispatch.t view on Meta::CPAN
# Should use the default serializer, YAML
my $t = Test::Rest->new( 'content_type' => 'text/plain' );
use_ok 'Catalyst::Test', 'Test::Catalyst::Action::REST';
foreach my $endpoint (qw/ test other_test /) {
foreach my $method (qw(GET DELETE POST PUT OPTIONS)) {
my $run_method = lc($method);
my $res;
if ( grep /$method/, qw(GET DELETE OPTIONS) ) {
$res = request( $t->$run_method( url => '/actions/' . $endpoint ) );
}
else {
$res = request(
$t->$run_method(
url => '/actions/' . $endpoint,
data => '',
)
);
}
ok( $res->is_success, "$method request succeeded" ) or warn Dumper($res);
view release on metacpan or search on metacpan
t/lib/Foo/Controller/Root.pm view on Meta::CPAN
push @{$c->stash->{body}}, 'explicit_detach';
$c->res->redirect('/success');
$c->detach;
}
sub explicit_detach_endpoint : Chained('explicit_detach') PathPart('endpoint') Args(0) {
my($self, $c) = @_;
push @{$c->stash->{body}}, 'endpoint';
return;
}
sub pitch_go : Chained('base') Args(0) ActionClass('DetachOnDie') {
my ( $self, $c ) = @_;
view release on metacpan or search on metacpan
lib/Catalyst/ActionRole/Tabs.pm view on Meta::CPAN
[% END %]
</ul>
=head1 DESCRIPTION
This module allows to add 'Tab' attributes to action endpoints, and it
will automatically build a data structure suitable for rendering 'tabs'
to switch between the methods that share the same tab structure.
Although this was originally built to help with making tabbed interfaces,
it isn't limited to creating tabs, as it simply collects the information
view release on metacpan or search on metacpan
lib/Catalyst/Authentication/Credential/OAuth.pm view on Meta::CPAN
Catalyst::Exception->throw( "Provider is not defined." )
unless defined $auth_info->{provider} || defined $self->providers->{ $auth_info->{provider} };
my $provider = $self->providers->{ $auth_info->{provider} };
for ( qw/ consumer_key consumer_secret request_token_endpoint access_token_endpoint user_auth_endpoint / ) {
Catalyst::Exception->throw( $_ . " is not defined for provider ". $auth_info->{provider} )
unless $provider->{$_};
}
my %defaults = (
view release on metacpan or search on metacpan
t/Consumer/lib/TestApp/Controller/Root.pm view on Meta::CPAN
},
setup_url => $c->uri_for($c->req->path, {moo => "setup"}),
server_secret => $c->config->{startup_time},
);
# From your OpenID server endpoint:
my ( $type, $data ) = $nos->handle_page;
if ($type eq "redirect")
{
view release on metacpan or search on metacpan
lib/Catalyst/Controller/DBIC/API.pm view on Meta::CPAN
item_root => 'data',
use_json_boolean => 1,
return_object => 1,
);
# Provides the following functional endpoints:
# /api/rpc/artist/create
# /api/rpc/artist/list
# /api/rpc/artist/id/[id]/delete
# /api/rpc/artist/id/[id]/update
=head1 DESCRIPTION
Easily provide common API endpoints based on your L<DBIx::Class> schema classes.
Module provides both RPC and REST interfaces to base functionality.
Uses L<Catalyst::Action::Serialize> and L<Catalyst::Action::Deserialize> to
serialize response and/or deserialise request.
=head1 OVERVIEW
This document describes base functionlity such as list, create, delete, update
and the setting of config attributes. L<Catalyst::Controller::DBIC::API::RPC>
and L<Catalyst::Controller::DBIC::API::REST> describe details of provided
endpoints to those base methods.
You will need to create a controller for each schema class you require API
endpoints for. For example if your schema has Artist and Track, and you want to
provide a RESTful interface to these, you should create
MyApp::Controller::API::REST::Artist and MyApp::Controller::API::REST::Track
which both subclass L<Catalyst::Controller::DBIC::API::REST>.
Similarly if you wanted to provide an RPC style interface then subclass
L<Catalyst::Controller::DBIC::API::RPC>. You then configure these individually
view release on metacpan or search on metacpan
lib/Catalyst/Controller/FlashRemoting.pm view on Meta::CPAN
Flash Remoting is RPC subsystem and that use AMF (Action Message Format) as message body format.
=head1 USAGE
At first, you need api gateway (endpoint) controller. Add AMFGateway attribute to catalyst action for that.
sub gateway :Local :AMFGateway { }
If you write above code in Root controller, then 'http://localhost:3000/gateway' is AMF Gateway url.
view release on metacpan or search on metacpan
lib/Catalyst/Action/SOAP/DocumentLiteralWrapped.pm view on Meta::CPAN
__PACKAGE__->{config}{soap_action_prefix} = 'http://foo/bar/';
use base 'Catalyst::Controller::SOAP::DocumentLiteralWrapped';
# or
sub endpoint : Local ActionClass(SOAP::DocumentLiteralWrapped) { }
=head1 DESCRIPTION
Microsoft has defined a pseudo-standard for SOAP usage called
Document/Literal Wrapped. This standard is a deviation of both the
view release on metacpan or search on metacpan
lib/Catalyst/ControllerRole/URI.pm view on Meta::CPAN
after 'register_action_methods', sub {
my ( $self, $app, @methods ) = @_;
my $class = ref $self;
my @endpoints = ();
my @types = @{ $app->dispatcher->dispatch_types ||+[] };
foreach my $type (@types) {
if(ref($type) eq 'Catalyst::DispatchType::Chained') {
foreach my $endpoint(@{ $type->{_endpoints} || [] }) {
if ($endpoint->class eq $class) {
push @endpoints, [$endpoint, $self->_generate_uri_pattern($type, $endpoint)];
}
}
}
}