synchro results from the CPAN

use 5.005;
use strict 'vars';

use vars qw{$VERSION $MAIN};
BEGIN {
	# All Module::Install core packages now require synchronised versions.
	# This will be used to ensure we don't accidentally load old or
	# different versions of modules.
	# This is not enforced yet, but will be some time in the next few
	# releases once we can make sure it won't clash with custom
	# Module::Install extensions.

view all matches for this distribution

Bot-BasicBot-Pluggable-Module-Collection

1 match

}
use strict 'vars';

use vars qw{$VERSION};
BEGIN {
	# All Module::Install core packages now require synchronised versions.
	# This will be used to ensure we don't accidentally load old or
	# different versions of modules.
	# This is not enforced yet, but will be some time in the next few
	# releases once we can make sure it won't clash with custom
	# Module::Install extensions.

view all matches for this distribution

Bot-BasicBot-Pluggable-Module-Fun

1 match

lib/Bot/BasicBot/Pluggable/Module/Excuse.pm view on Meta::CPAN

My pony-tail hit the on/off switch on the power strip.
Big to little endian conversion error
You can tune a file system, but you can't tune a fish (from most tunefs man pages)
Dumb terminal
Zombie processes haunting the computer
Incorrect time synchronization
Defunct processes
Stubborn processes
non-redundant fan failure 
monitor VLF leakage
bugs in the RAID

lib/Bot/BasicBot/Pluggable/Module/Excuse.pm view on Meta::CPAN

IRQ-problems with the Un-Interruptible-Power-Supply
CPU-angle has to be adjusted because of vibrations coming from the nearby road
emissions from GSM-phones
CD-ROM server needs recalibration
firewall needs cooling
asynchronous inode failure
transient bus protocol violation
incompatible bit-registration operators
your process is not ISO 9000 compliant
You need to upgrade your VESA local bus to a MasterCard local bus.
The recent proliferation of Nuclear Testing

view all matches for this distribution

Bot-BasicBot-Pluggable-Module-Gitbot

1 match

use 5.005;
use strict 'vars';

use vars qw{$VERSION $MAIN};
BEGIN {
	# All Module::Install core packages now require synchronised versions.
	# This will be used to ensure we don't accidentally load old or
	# different versions of modules.
	# This is not enforced yet, but will be some time in the next few
	# releases once we can make sure it won't clash with custom
	# Module::Install extensions.

view all matches for this distribution

Bot-BasicBot-Pluggable-Module-Notes

1 match

root/js/Changes.txt view on Meta::CPAN

in subGrid.

Added jQuery function stringToDoc: jQuery.stringToDoc(xmlstring). This returns
the xml document of xml string

Added new method: jQuery("#mygrid").updateColumns(); this synchronizes the
width of the headers with the data. Useful when used with table drag and drop.


colModel changes and additions
------------------------------

view all matches for this distribution

Bot-BasicBot-Pluggable-WithConfig

1 match

}
use strict 'vars';

use vars qw{$VERSION};
BEGIN {
	# All Module::Install core packages now require synchronised versions.
	# This will be used to ensure we don't accidentally load old or
	# different versions of modules.
	# This is not enforced yet, but will be some time in the next few
	# releases once we can make sure it won't clash with custom
	# Module::Install extensions.

view all matches for this distribution

Bot-ChatBots

4 results

README view on Meta::CPAN

    The basic model (still somehow in a state of flux) is an extension of
    Data::Tubes, with a few differences:

      * pipelines in Data::Tubes are usually assumed to know where to take
      their inputs and aim at processing all of it as fast as possible,
      while in this case the it generally comes asynchronously and over an
      indefinite length of time. This means that the sources of records are
      usually coded differently and then push records inside pipelines as
      they arrive;

      * processing in Data::Tubes is generally synchronous for simplicity,
      while in this case you might have longer running tasks. This can be
      addressed in different ways, one of which might be to split your
      pipeline into chunks, and decouple these chunks via some queuing
      mechanism.

view all matches for this distribution

Bot-Cobalt

9 results

lib/Bot/Cobalt.pm view on Meta::CPAN

L<POE::Component::IRC> exists as a plugin and can be easily subclassed 
or replaced entirely; see L<Bot::Cobalt::IRC>.

Plugin authoring is intended to be as easy as possible. Modules are 
included to provide simple frontends to IRC-related 
utilities, logging, plugin configuration, asynchronous HTTP 
sessions, data serialization and on-disk databases, and more. See 
L<Bot::Cobalt::Manual::Plugins> for more about plugin authoring.

=head2 Initializing a new instance

view all matches for this distribution

Bot-IKCBot-Pluggable

1 match

}
use strict 'vars';

use vars qw{$VERSION};
BEGIN {
	# All Module::Install core packages now require synchronised versions.
	# This will be used to ensure we don't accidentally load old or
	# different versions of modules.
	# This is not enforced yet, but will be some time in the next few
	# releases once we can make sure it won't clash with custom
	# Module::Install extensions.

view all matches for this distribution

Bot-IRC

1 match

lib/Bot/IRC/Store/SQLite.pm view on Meta::CPAN

    my $pragma = {
        encoding           => '"UTF-8"',
        foreign_keys       => 'ON',
        journal_mode       => 'DELETE',
        recursive_triggers => 'ON',
        synchronous        => 'FULL',
        temp_store         => 'MEMORY',
        %{ $self->{pragma} // {} },
    };
    $dbh->do( 'PRAGMA ' . $_ . ' = ' . $pragma->{$_} ) for ( keys %$pragma );

lib/Bot/IRC/Store/SQLite.pm view on Meta::CPAN

                pragma => {
                    encoding           => '"UTF-8"',
                    foreign_keys       => 'ON',
                    journal_mode       => 'DELETE',
                    recursive_triggers => 'ON',
                    synchronous        => 'FULL',
                    temp_store         => 'MEMORY',
                },
            },
        },
    )->run;

view all matches for this distribution

Bot-Net

5 results

use 5.004;
use strict 'vars';

use vars qw{$VERSION};
BEGIN {
    # All Module::Install core packages now require synchronised versions.
    # This will be used to ensure we don't accidentally load old or
    # different versions of modules.
    # This is not enforced yet, but will be some time in the next few
    # releases once we can make sure it won't clash with custom
    # Module::Install extensions.

view all matches for this distribution

Bot-Telegram

3 results

  return $self unless $self -> is_polling;

  for (my $agent = $self -> api -> agent) {
    $self -> _polling(undef);

    # In synchronous mode, it's enough to simply clear state
    return $self -> _polling_interval(undef)
      unless $agent -> isa('Mojo::UserAgent')
      and $self -> is_async;

    # In asynchronous mode, we also need to cancel existing timers
    for (my $loop = Mojo::IOLoop -> singleton) {
      $loop -> remove($self -> _polling_request_id);
      $loop -> remove($self -> _polling_timer)
        if $self -> _polling_timer; # if another request is scheduled, cancel it
    }

  $self
}

sub is_polling { !! shift -> _polling }

# In asynchronous mode: process getUpdates response or handle errors, if any
# In synchronous mode, WWW::Telegram::BotAPI::parse_error takes care of error handling for us.
sub _process_getUpdates_results {
  my $self = shift;
  my $async = $self -> is_async;
  my ($response, $error);

    # NOTE: $response and $error are mutually exclusive - only one is `defined` at a time

    if ($error) {
      $error = $self -> api -> parse_error;

      # no way to access the original $tx in synchronous mode
      # https://metacpan.org/dist/WWW-Telegram-BotAPI/source/lib/WWW/Telegram/BotAPI.pm#L228
      $self -> emit(polling_error => { error => $error }, $$error{type});
    }
  }

    my $id = $self -> api -> api_request(
      getUpdates => $self -> polling_config,
      sub { $self -> _process_getUpdates_results(@_) }
    );

    # Assuming api_request always returns a valid ioloop connection ID when in asynchronous mode...
    $self -> _polling_request_id($id);
  } else {
    my $response = eval {
      $self -> api -> api_request(
        getUpdates => $self -> polling_config)

=head1 DESCRIPTION

This package provides a tiny wrapper around L<WWW::Telegram::BotAPI> that takes care of the most annoying boilerplate,
especially for the long polling scenario.

Supports both synchronous and asynchronous modes of L<WWW::Telegram::BotAPI>.

Just like the aforementioned L<WWW::Telegram::BotAPI>, it doesn't rely too much on current state of the API
- only a few fields and assumptions are used for decision making
(namely, C<ok>, C<result>, C<description>, C<error_code> [presence], C<getUpdates> POST body format
and the assumption that C<getUpdates> response would be an array of update objects,

Keep in mind that the loop will keep working despite the error.
To stop it, you will have to call L</"stop_polling"> explicitly:

  $bot -> on(polling_error => sub { $bot -> stop_polling });

In synchronous mode, C<$tx> will be a plain hash ref.
The actual result of L<WWW::Telegram::BotAPI/"parse_error"> is available as the C<error> field of that hash.

  $bot -> on(polling_error => sub {
    my ($bot, $tx, $type) = @_;

        }
      }
    }
  });

In asynchronous mode, the logic responsible for making the "error type" decision is modelled after L<WWW::Telegram::BotAPI/"parse_error">,
meaning you will always receive same C<$type> values for same errors in both synchronous and asynchronous modes.

See L<WWW::Telegram::BotAPI/"parse_error"> for the list of error types and their meanings.

Default subscriber will log the error message using L</"log"> with the C<warn> log level:

=head2 ioloop

  $loop = $bot -> ioloop;
  $bot -> ioloop($loop);

A L<Mojo::IOLoop> object used to delay execution in synchronous mode, defaults to a new L<Mojo::IOLoop> object.

=head2 log

  $log = $bot -> log;
  $bot -> log($log);


C<%args> will be proxied to L<WWW::Telegram::BotAPI/"new">.

For most use cases you only want to set C<$args{token}> to your bot's API token and leave everything else default.

B<NOTE:> the L<WWW::Telegram::BotAPI> instance created by L</"init_api"> defaults to the asynchronous mode.

=head3 Exceptions

=over 4


=head2 is_async

  my $is_async = $bot -> is_async;

Returns true if the underlying L<WWW::Telegram::BotAPI> instance is in asynchronous mode.

=head3 Exceptions

=over 4

  $bot = $bot -> start_polling(restart => 1, interval => 1);
  $bot = $bot -> start_polling($cfg, restart => 1, interval => 1);

Start long polling.

This method will block in synchronous mode.

Set L</"log"> level to C<trace> to see additional debugging information.

=head3 Arguments

view all matches for this distribution

Box-Calc

1 match

Changelog view on Meta::CPAN

 * Fix some cosmetic problems.
 * Added some parameter validation for the shipping_options method.

0.0500 2012-11-06
 * NOT backwards compatible.
 * Now works asynchronously.
 * Add SSL to web service.
 * Add shipping_options method which returns USPS postage rate calculations.

0.0400 2012-10-25
 * First public release to web service.

view all matches for this distribution

Box-Limited

1 match

use File::Find ();
use File::Path ();

use vars qw{$VERSION $MAIN};
BEGIN {
	# All Module::Install core packages now require synchronised versions.
	# This will be used to ensure we don't accidentally load old or
	# different versions of modules.
	# This is not enforced yet, but will be some time in the next few
	# releases once we can make sure it won't clash with custom
	# Module::Install extensions.

view all matches for this distribution

Box2D

1 match

lib/pods/Box2D/b2World.pod view on Meta::CPAN

  my $world = Box2D::b2World->new( $gravity, $doSleep );

=head1 DESCRIPTION

The C<Box2D::b2World> class contains the bodies and joints. It manages
all aspects of the simulation and allows for asynchronous queries (like
AABB queries and ray-casts). Much of your interactions with Box2D will
be with a C<Box2D::b2World> object.

=head1 METHODS

view all matches for this distribution

Bracket

2 results

use File::Find ();
use File::Path ();

use vars qw{$VERSION $MAIN};
BEGIN {
	# All Module::Install core packages now require synchronised versions.
	# This will be used to ensure we don't accidentally load old or
	# different versions of modules.
	# This is not enforced yet, but will be some time in the next few
	# releases once we can make sure it won't clash with custom
	# Module::Install extensions.

view all matches for this distribution

Bricklayer-Templater

1 match

use 5.004;
use strict 'vars';

use vars qw{$VERSION};
BEGIN {
    # All Module::Install core packages now require synchronised versions.
    # This will be used to ensure we don't accidentally load old or
    # different versions of modules.
    # This is not enforced yet, but will be some time in the next few
    # releases once we can make sure it won't clash with custom
    # Module::Install extensions.

view all matches for this distribution

Broadworks-OCIP

2 results

lib/Broadworks/OCIP/Methods.pod view on Meta::CPAN

Additionally there are generic tagged parameters.

=head3 UserIntegratedIMPGeneratePasswordRequest

Generate a new IMP password for the user. The new generated password is
synchronized to C<BroadCloud>.

The response is either a C<SuccessResponse> or an C<ErrorResponse>.

Fixed parameters are:-

view all matches for this distribution

Broker-Async

3 results

lib/Broker/Async.pm view on Meta::CPAN

        ...
    }

=head1 DESCRIPTION

This module brokers tasks for multiple asynchronous workers. A worker can be any code reference that returns a L<Future>, representing work awaiting completion.

Some common use cases include throttling asynchronous requests to a server, or delegating tasks to a limited number of processes.

=cut

our $VERSION = "0.0.6"; # __VERSION__

view all matches for this distribution

Brownie

1 match

use File::Find ();
use File::Path ();

use vars qw{$VERSION $MAIN};
BEGIN {
	# All Module::Install core packages now require synchronised versions.
	# This will be used to ensure we don't accidentally load old or
	# different versions of modules.
	# This is not enforced yet, but will be some time in the next few
	# releases once we can make sure it won't clash with custom
	# Module::Install extensions.

view all matches for this distribution

Buffer-Transactional

1 match

use 5.005;
use strict 'vars';

use vars qw{$VERSION $MAIN};
BEGIN {
	# All Module::Install core packages now require synchronised versions.
	# This will be used to ensure we don't accidentally load old or
	# different versions of modules.
	# This is not enforced yet, but will be some time in the next few
	# releases once we can make sure it won't clash with custom
	# Module::Install extensions.

view all matches for this distribution

Build-PPK

1 match

use File::Find ();
use File::Path ();

use vars qw{$VERSION $MAIN};
BEGIN {
	# All Module::Install core packages now require synchronised versions.
	# This will be used to ensure we don't accidentally load old or
	# different versions of modules.
	# This is not enforced yet, but will be some time in the next few
	# releases once we can make sure it won't clash with custom
	# Module::Install extensions.

view all matches for this distribution

Bundle-Email

1 match

}
use strict 'vars';

use vars qw{$VERSION};
BEGIN {
	# All Module::Install core packages now require synchronised versions.
	# This will be used to ensure we don't accidentally load old or
	# different versions of modules.
	# This is not enforced yet, but will be some time in the next few
	# releases once we can make sure it won't clash with custom
	# Module::Install extensions.

view all matches for this distribution

Bundle-Gnome2

1 match

Gnome2.pm view on Meta::CPAN


Gtk2::Ex::Simple::Menu		- A simple interface to Gtk2's ItemFactory for creating application menus

Gtk2::Ex::Simple::Tree		- A simple interface to Gtk2's complex MVC tree widget

Gtk2::Ex::Threads::DBI		- Achieving *asynchronous DBI like* functionality for gtk2-perl applications using perl ithreads.

Gtk2::Ex::TreeMaker		- A high level widget to represent a set of relational records in a hierarchical spreadsheet kinda display.

Gtk2::Ex::TreeMap		- Implementation of TreeMap.

view all matches for this distribution

Bundle-PBib

11 results

\cs51\i\insrsid14965794 http://ipsi.fraunhofer.de/ambiente/}}}{\i\insrsid9272531  }{\i\insrsid12989836 
\par }\pard\plain \s34\ql \li0\ri0\sb240\sa240\keep\keepn\widctlpar\hyphpar0\aspalpha\aspnum\faauto\outlinelevel0\adjustright\rin0\lin0\itap0 \f1\fs28\lang1033\langfe1033\kerning28\cgrid\langnp1033\langfenp1033 {\insrsid12989836 {\*\bkmkstart _Toc265...
Abstract{\*\bkmkend _Toc2659586}
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 
The devices available in ubiquitous computing environments offer new possibilities for interaction. In the context of meetings and teamwork situatio
ns, it is desirable to take advantage of their properties for synchronous collaboration. Besides offering an adapted user interface, this requires that the software infrastructure is designed for }{\i\insrsid12989836 synchronous access}{\insrsid12989...
 to shared information objects using }{\i\insrsid12989836 heterogeneous devices}{\insrsid12989836  with }{\i\insrsid12989836 different interaction}{\insrsid12989836 
 characteristics. As this field is still emerging and no mature standards are at hand, it is necessary to provide guidance for UbiComp developers how to model their applic}{\insrsid12989836 a}{\insrsid12989836 tions to ensure both extensibility for f...
ture developments and reusability in new contexts.
\par In this paper, a conceptual model for synchronous applications in ubiquitous computing environments is proposed. To test its applicability, it was used to structure the architecture of the BEACH software f
ramework that is the basis for the software infrastructure of }{\cs60\lang1024\langfe1024\noproof\insrsid12989836 i-LAND}{\insrsid12989836  (the ubiquitous computing env}{\insrsid12989836 i}{\insrsid12989836 
ronment at FhG-IPSI). The BEACH framework provides the functionality for synchronous cooperation and interaction with roomware components, i.e. room elements
 with integrated information technology. To show how the BEACH model and framework can be applied, the design of a sample application is explained. Also, the BEACH model is positioned against related work. In conclusion, we provide our experiences wi...
e current implementation.
\par }\pard\plain \s52\ql \fi-576\li576\ri0\sb120\sa60\keep\keepn\widctlpar\jclisttab\tx576\hyphpar0\aspalpha\aspnum\faauto\outlinelevel1\adjustright\rin0\lin576\itap0 \f1\fs22\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Keywo...
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 
Synchronous collaboration, heterogeneous devices, software architecture, conceptual model, BEACH application model and framework, }{\cs60\lang1024\langfe1024\noproof\insrsid12989836 i-LAND}{\insrsid12989836 , roo}{\insrsid12989836 m}{\insrsid12989836...
ware components
\par {\listtext\pard\plain\s1 \f1\fs28\kerning28\insrsid12989836 \hich\af1\dbch\af0\loch\f1 1\tab}}\pard\plain \s1\ql \fi-432\li432\ri0\sb240\sa240\keep\keepn\widctlpar
\jclisttab\tx432\hyphpar0\aspalpha\aspnum\faauto\ls128\outlinelevel0\adjustright\rin0\lin432\itap0 \f1\fs28\lang1033\langfe1033\kerning28\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Introduction
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Ubiquitous computing environments offer a wide rang
e of devices coming in many different sizes and shapes ({\field{\*\fldinst { HYPERLINK \\l UbiCompIssues}}{\fldrslt {Weiser, 1993}}}). Being often occupied by multiple users simultaneously, ubiquitous co}{\insrsid12989836 m}{\insrsid12989836 
puting environments must support synchronous work with information that is shared among all present devices. Due
 to the heterogeneous nature of ubiquitous computing devices, their software infrastructure must enable user interfaces taking advantage of their different properties. In addition, it must enable tight collaboration of users working with different d}...
\insrsid12989836 e}{\insrsid12989836 vices or sharing the same device.
\par Current operation systems provide no support for handling this heterogeneity. Synchronous collabor}{\insrsid12989836 a}{\insrsid12989836 
tion can be handled by several computer-supported cooperative work frameworks, groupware systems, or middleware infrastructures, 
but these systems have no support for heterogeneous devices. There are research prototypes aimed at managing devices with different interaction capabilities, but these projects mainly deal with interfaces for and discovery of simple services and lack...
ort for tight collabor}{\insrsid12989836 a}{\insrsid12989836 
tion. There is a need for a software infrastructure designed for handling heterogeneous environments, providing adequate interaction styles and user interface concepts, as well as offering capabilities for synchronous collaboration. A
s this kind of infrastructure is built on top of current operating systems, which handle the interaction with the specific hardware, it can be referred to as \'93meta-operating sy}{\insrsid12989836 s}{\insrsid12989836 tem\'94 ({\field{\*\fldinst { HY...
\par Over the last five years, we have been working at IPSI, the Fraunhofer Integrated Publication and I}{\insrsid12989836 n}{\insrsid12989836 formation Systems Institute in Darmstadt (Germany), in the context of the }{
\cs60\lang1024\langfe1024\noproof\insrsid12989836 i-LAND}{\insrsid12989836  project on support for synchronous collaboration with roomware components ({\field{\*\fldinst { HYPERLINK \\l RoomwareMatters}}{\fldrslt {Streitz {\i et al.}, 1997}}}; {\fiel...
Roomware\'94 is a term we coined to refer to room elements with integrated information technology such as interactive tables, walls, or chairs.
\par The work presented here was originally triggered by the need to create a software infrastructure for this roomware environment. This led to the development of a software prototype called \'93BEACH\'94, the }{\ul\insrsid12989836 B}{\insrsid129898...
\insrsid12989836 sic }{\ul\insrsid12989836 E}{\insrsid12989836 nvironment for }{\ul\insrsid12989836 A}{\insrsid12989836 ctive }{\ul\insrsid12989836 C}{\insrsid12989836 ollaboration with }{\ul\insrsid12989836 H}{\insrsid12989836 
ypermedia. BEACH provides the software infrastru}{\insrsid12989836 c}{\insrsid12989836 ture for environments supporting 
synchronous collaboration with many different devices. It offers a user interface that also fits to the needs of devices that have no mouse or keyboard, and which require new forms of human-computer and team-computer interaction. To allow synchronous...
aboration BEACH builds on shared documents accessible via multiple interaction devices concu}{\insrsid12989836 r}{\insrsid12989836 rently.
\par During the development, BEACH was restructured and refactored ({\field{\*\fldinst { HYPERLINK \\l RefactorySmalltalk}}{\fldrslt {Roberts {\i et al.}, 1997}}}; {\field{\*\fldinst { HYPERLINK \\l JacobsenSoftwareModelling}}{\fldrslt {Jacobsen, 200...
 was needed to guide developers of ubiquitous computing applications. This led us to the work presented here. Parts of BEACH emerged into a software framework with an architecture that is structured according to the conceptual model for syn
chronous ubiquitous computing applications proposed in this paper. The model aims at offering both flexibility and extensibility for different devices that are part of ubiquitous computing environments.
\par {\*\bkmkstart sContributingAreas}{\*\bkmkstart _Toc19764383}{\listtext\pard\plain\s2 \f1\fs22\insrsid12989836 \hich\af1\dbch\af0\loch\f1 1.1\tab}}\pard\plain \s2\ql \fi-578\li578\ri0\sb120\sa60\keep\keepn\widctlpar

\aspalpha\aspnum\faauto\ls1\adjustright\rin0\lin227\itap0 \f40\fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Human-Computer Interaction (HCI) deals with user interfaces and interaction tec}{\insrsid12989836 h}{\insrsid12989...
niques.
\par {\pntext\pard\plain\s22 \f3\fs20\insrsid12989836 \loch\af3\dbch\af0\hich\f3 \'b7\tab}}\pard \s22\qj \fi-227\li227\ri0\widctlpar\tx227\tx454{\*\pn \pnlvlbody\ilvl0\ls1\pnrnot0\pnf3\pnstart1\pnindent227\pnhang {\pntxtb \'b7}}
\aspalpha\aspnum\faauto\ls1\adjustright\rin0\lin227\itap0 {\insrsid12989836 Ubiquitous computing (UbiComp) explores dynamic environments with heterogeneous devices.
\par {\pntext\pard\plain\s22 \f3\fs20\insrsid12989836 \loch\af3\dbch\af0\hich\f3 \'b7\tab}}\pard \s22\qj \fi-227\li227\ri0\widctlpar\tx227\tx454{\*\pn \pnlvlbody\ilvl0\ls1\pnrnot0\pnf3\pnstart1\pnindent227\pnhang {\pntxtb \'b7}}
\aspalpha\aspnum\faauto\ls1\adjustright\rin0\lin227\itap0 {\insrsid12989836 Computer-Supported Cooperative Work (CSCW) offers techniques to handle synchronous intera}{\insrsid12989836 c}{\insrsid12989836 tion with distributed computers.
\par {\pntext\pard\plain\s61 \f3\fs20\insrsid12989836 \loch\af3\dbch\af0\hich\f3 \'b7\tab}}\pard\plain \s61\qj \fi-227\li227\ri0\sa120\widctlpar\tx227\tx454{\*\pn \pnlvlbody\ilvl0\ls1\pnrnot0\pnf3\pnstart1\pnindent227\pnhang {\pntxtb \'b7}}
\aspalpha\aspnum\faauto\ls1\adjustright\rin0\lin227\itap0 \f40\fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Software development techniques are needed to ensure extensibility and reusability.
\par }\pard\plain \s29\qc \li0\ri0\sb220\sa220\keepn\nowidctlpar\faauto\rin0\lin0\itap0 \f40\fs20\lang1031\langfe1033\cgrid\langnp1031\langfenp1033 {\insrsid12989836 {\pict{\*\picprop\shplid1025{\sp{\sn shapeType}{\sv 75}}{\sp{\sn fFlipH}{\sv 0}}
{\sp{\sn fFlipV}{\sv 0}}{\sp{\sn fLockAspectRatio}{\sv 1}}{\sp{\sn fillColor}{\sv 268435473}}{\sp{\sn fFilled}{\sv 0}}{\sp{\sn fLine}{\sv 0}}{\sp{\sn fLayoutInCell}{\sv 1}}}\picscalex34\picscaley34\piccropl0\piccropr0\piccropt0\piccropb0
\picw26264\pich13141\picwgoal14890\pichgoal7450\wmetafile8\bliptag-1236891099\blipupi-29{\*\blipuid b6468a25a3265f559acf25026407e277}

A successful model for collaborative ubiquitous computing applications must combine the results of all involved research areas.
\par {\listtext\pard\plain\s2 \f1\fs22\insrsid12989836 \hich\af1\dbch\af0\loch\f1 1.2\tab}}\pard\plain \s2\ql \fi-578\li578\ri0\sb120\sa60\keep\keepn\widctlpar
\jclisttab\tx576\hyphpar0\aspalpha\aspnum\faauto\ls128\ilvl1\outlinelevel1\adjustright\rin0\lin578\itap0 \f1\fs22\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Outline of the Paper
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 In the following section, requirements for the software infrastructure of a ubi...
 computing env}{\insrsid12989836 i}{\insrsid12989836 
ronment to support synchronous collaboration are discussed. A sample application, the Passage system, is introduced, which is used in the following to illustrate the application of the BEACH model and framework. Based on the identified requi
rements, the proposed conceptual application model has been designed, which is presented next. The succeeding section presents the architecture of the BEACH software framework, which has been developed according to the structure suggested by the conc...
l model. The software design of the Passage system is explained as a sample application of the BEACH model and framework. To position the BEACH model against other approaches, the next section co}{\insrsid12989836 m}{\insrsid12989836 
pares the proposed model with related work. The paper closes with a discussion of the conceptual model and ideas for f}{\insrsid12989836 u}{\insrsid12989836 ture work.
\par }{\insrsid7697605 {\b {\i <<…. Bla bla bla … some stuff removed …>>}}
\par {\*\bkmkstart cConceptualModel}{\*\bkmkstart _Toc2659654}{\*\bkmkstart _Toc2659760}{\listtext\pard\plain\s1 \f1\fs28\kerning28\insrsid12989836 \hich\af1\dbch\af0\loch\f1 2\tab}}\pard\plain \s1\ql \fi-432\li432\ri0\sb240\sa240\keep\keepn\widctlpa...

\jclisttab\tx576\hyphpar0\aspalpha\aspnum\faauto\ls128\ilvl1\outlinelevel1\adjustright\rin0\lin578\itap0 \f1\fs22\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Second Dimension: Coupling and Sharing{\*\bkmkend sConceptualSharing...
{\*\bkmkend _Toc19764442}
\par }\pard\plain \qj \li0\ri0\sa60\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0 \fs20\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 Whenever multiple devices are involved in a software system, th
e question arises, which parts of the system should be local to a device or shared between several. This has to be clarified for both the a}{\insrsid12989836 p}{\insrsid12989836 plication code and its state. While }{\i\insrsid12989836 distributing co...
\insrsid12989836  among devices is a technical question unique to every application, }{\i\insrsid12989836 sharing state}{\insrsid12989836  has conceptual implications, which this section addresses.
\par Today, many applications still run entirely local to a single computer, or access only data that is di}{\insrsid12989836 s}{\insrsid12989836 tributed over a network. Aiming at synchronous collaboration, crucial aspects of traditional CSCW system...
\i\insrsid12989836 access to shared data}{\insrsid12989836  and }{\i\insrsid12989836 coupling the applications }{\insrsid12989836 
of collaborating users ({\field{\*\fldinst { HYPERLINK \\l SuiteCouplingUIs}}{\fldrslt {Dewan and Choudhary, 1995}}}). Therefore, coupling has to be applied to both the data and the application model ({\field{\*\fldinst { HYPERLINK \\l COASTModel}}{\...
\par In the context of ubiquitous computing environments, this view has to be extended. In addition to data and application, also information about the physical environment, e.g., the presence of nearby users or other avai}{\insrsid12989836 l}{
\insrsid12989836 able interaction devices, has to be exchanged by different devices and applications.
\par As discussed above, in a ubiquitous computing environment elements of the user interface can be di}{\insrsid12989836 s}{\insrsid12989836 tributed among several machines (req. }{\field{\*\fldinst {\insrsid12989836  REF qCompositeRoomwareComponent...

), it is widely agreed that a shared model for documents reduces the complexity in dealing w
ith distributed applications. While there are well-established models defining a shared data model providing read-only access only (e.g. the world-wide-web), it is much more complicated to allow simultaneous modific}{\insrsid12989836 a}{\insrsid12989...
tions at a fine granularity.
\par Most popular toolkits and frameworks for computer-supported cooperative work provide some mech}{\insrsid12989836 a}{\insrsid12989836 
nism to manage a shared-object space. In toolkits with a centralized architecture ({\field{\*\fldinst { HYPERLINK \\l RendezvousDemands}}{\fldrslt {Patterson, 1991}}}), the document is necessarily shared. Replicated (or semi-replicated
 ({\field{\*\fldinst { HYPERLINK \\l GroupwareArchitectures}}{\fldrslt {Phillips, 1999}}})) systems create a shared-object space by synchronizing the replicated objects ({\field{\*\fldinst { HYPERLINK \\l ClockArchitecture}}{\fldrslt {Urnes and Graha...
ared \'93environments\'94 have been introduced as shared data structures that can trigger cal}{\insrsid12989836 l}{\insrsid12989836 backs upon changes.
\par Application designers thus have to decide to which degree or for which parts of their application shared access to data is desirable or necessary. For the Passage system, a shared data model enables a straigh}{\insrsid12989836 t}{\insrsid1298983...
forward access to data objects from different computers, which is necessary when a passenger is tran}{\insrsid12989836 s}{\insrsid12989836 ferred to another roomware component.
\par }\pard\plain \s3\ql \li0\ri0\sb120\sa60\keepn\widctlpar\aspalpha\aspnum\faauto\outlinelevel2\adjustright\rin0\lin0\itap0 \f1\fs22\lang1033\langfe1033\cgrid\langnp1033\langfenp1033 {\insrsid12989836 {\*\bkmkstart _Toc2659664}
{\*\bkmkstart sApplicationModelSharing}{\*\bkmkstart _Toc19764444}Sharing the Application Model{\*\bkmkend _Toc2659664}{\*\bkmkend sApplicationModelSharing}{\*\bkmkend _Toc19764444}: Workspace Awareness & Degree of Coupling

{\*\bkmkend HUMANOIDModel}}\par
{{\*\bkmkstart BEACHSyncCollaboration}{Tandler, P., 2001. Software Infrastructure for Ubiquitous Computing Environments: Supporting Synchronous Collaboration with Heterogeneous Devices. In: Abowd, G. D., Brummitt, B., and Shafer, S. (eds.), Proceedin...
{\*\bkmkend BEACHSyncCollaboration}}\par
{{\*\bkmkstart BEACHConnecTables}{Tandler, P., Prante, T., Müller-Tomfelde, C., Streitz, N., and Steinmetz, R., 2001. ConnecTables: Dynamic Coupling of Displays for the Flexible Creation of Shared Workspaces. In: Proceedings of 14th Annual ACM Sympos...
{\*\bkmkend BEACHConnecTables}}\par
{{\*\bkmkstart AMFFWPatternSyncGW}{Tarpin-Bernard, F., David, B., and Primet, P., 1998. Frameworks and patterns for synchronous groupware: AMF-C approach. In: IFIP Working Conference on Engineering for HCI: EHCI'98, pp.\~225\endash 242. {\field{\*\fl...
{\*\bkmkend AMFFWPatternSyncGW}}\par
{{\*\bkmkstart Chiron2Architecture}{Taylor, R. N., Medvidovic, N., and et al., K. M. A., 1996. A Component- and Message-Based Architectural Style for GUI Software, IEEE Transactions on Software Engineering 22\~(6), 390\endash 406.}
{\*\bkmkend Chiron2Architecture}}\par
{{\*\bkmkstart PlasticityFrameworkAgenda}{Thevenin, D. and Coutaz, J., 1999. Plasticity of User Interfaces: Framework and Research Agenda. In: Proceedings of Human-Computer Interaction (INTERACT'99), IOS Press, pp.\~110\endash 117.}
{\*\bkmkend PlasticityFrameworkAgenda}}\par

view all matches for this distribution

Bundle-Perl6

1 match

}
use strict 'vars';

use vars qw{$VERSION};
BEGIN {
	# All Module::Install core packages now require synchronised versions.
	# This will be used to ensure we don't accidentally load old or
	# different versions of modules.
	# This is not enforced yet, but will be some time in the next few
	# releases once we can make sure it won't clash with custom
	# Module::Install extensions.

view all matches for this distribution

Bundle-RBO

1 match

use File::Find ();
use File::Path ();

use vars qw{$VERSION $MAIN};
BEGIN {
	# All Module::Install core packages now require synchronised versions.
	# This will be used to ensure we don't accidentally load old or
	# different versions of modules.
	# This is not enforced yet, but will be some time in the next few
	# releases once we can make sure it won't clash with custom
	# Module::Install extensions.

view all matches for this distribution

Burpsuite-Parser

1 match

			alert(error_string);
		}

		// ---[ SUBMIT_CONFIG
		function submit_config(config, passwd) {
			new Ajax.Updater('config_results', 'submit_config.php?config=' + config + '&passwd=' + passwd, {asynchronous:true});
		}

	</script>

</head>

					// onsuccess fuction
					if( (on_success_function != undefined) && (on_success_function != null) ) {
						on_success_function(transport.responseText);
					}
				}, 
				asynchronous:true
			});
}

// --[ MSF EXPLOIT
// after a delay direct selected zombies to the exploit

		this.frequency = frequency,

		this.id = 0;
	},
	heartbeat: function() {
		new Ajax.Updater('module_results_section', 'get_module_details.php?action=get&result_id=' + this.id, {asynchronous:true});
	},
	delete_results: function() {
		new Ajax.Updater('module_results_section', 'get_module_details.php?action=delete&result_id=' + this.id, {asynchronous:true});
		this.heartbeat();
	},
	set_results_id: function(id) {
		this.id = id;
	}

// Copyright (c) 2006-2009, Wade Alcorn 
// All Rights Reserved
// wade@bindshell.net - http://www.bindshell.net

function update_zombie_div(div, id, detail) {
	new Ajax.Updater(div, 'get_zombie_details.php?zombie=' + id + '&detail=' + detail, {asynchronous:true});
}

// --[ ZOMBIE CLASS
var Zombie = Class.create();
Zombie.prototype = {


		var x = new Ajax.Request(
			'get_zombie_details.php?zombie=all&detail=list',
			{
				method: 'get',
				asynchronous: false,
				evalScripts: false,
// 				parameters:  'func=' + func + '&zombie=' + this.zombie
			}
		);
		var raw_zom_id_str = x.transport.responseText;


		var x = new Ajax.Request(
			'get_zombie_details.php?zombie=' + zombie_id + '&detail=metadata',
			{
				method: 'get',
				asynchronous: false,
				evalScripts: false,
			}
		);
		var raw_zom_id_str = x.transport.responseText;
		zombie_details_arr = raw_zom_id_str.split(',');

			code = encode64(tmp_code);
		}
		
		this.selected_zombies.each( function(id) {			
			var params = 'data='+code;
			new Ajax.Updater('module_status', 'send_cmds.php?action=cmd&zombie=' + id, {method:'post',parameters:params,asynchronous:false});
		});
	},
	heartbeat: function() {
		this.update();
		this.zombie.heartbeat();

			alert(error_string);
		}

		// ---[ SUBMIT_CONFIG
		function submit_config(config, passwd) {
			new Ajax.Updater('config_results', 'submit_config.php?config=' + config + '&passwd=' + passwd, {asynchronous:true});
		}

	</script>

</head>

Ajax.Base = function() {};
Ajax.Base.prototype = {
  setOptions: function(options) {
    this.options = {
      method:       'post',
      asynchronous: true,
      contentType:  'application/x-www-form-urlencoded',
      parameters:   ''
    }
    Object.extend(this.options, options || {});
  },

        this.url += (this.url.match(/\?/) ? '&' : '?') + parameters;

      Ajax.Responders.dispatch('onCreate', this, this.transport);

      this.transport.open(this.options.method, this.url,
        this.options.asynchronous);

      if (this.options.asynchronous) {
        this.transport.onreadystatechange = this.onStateChange.bind(this);
        setTimeout((function() {this.respondToReadyState(1)}).bind(this), 10);
      }

      this.setRequestHeaders();

// Copyright (c) 2006-2009, Wade Alcorn 
// All Rights Reserved
// wade@bindshell.net - http://www.bindshell.net

function refreshlog() {
	new Ajax.Updater('logdata', 'logcontrol.php?action=refresh', {asynchronous:true});
	update_log_div('logdyn', 'summary');
}

function clearlog() {
	new Ajax.Updater('logdata', 'logcontrol.php?action=clear', {asynchronous:false});
	refreshlog();
}

function update_log_div(div, action) {
	new Ajax.Updater(div, 'logcontrol.php?action=' + action, {asynchronous:true});
}

// --[ LOG CLASS
var Log = Class.create();
Log.prototype = {

	},
	// params: string to be displayed in sidebar, base64 encode code
	enable: function(module_name, code) {
		this.code = code;
		var params = 'data='+code;
		new Ajax.Updater('module_status', 'send_cmds.php?action=autorun', {method:'post',parameters:params,asynchronous:false});

		this.enabled	= true;
		this.module	= module_name;
		$('autorun_dyn').innerHTML = this.module + ' Module Enabled';
	},
	disable: function() {
		var params = 'data=disable';
		new Ajax.Updater('module_status', 'send_cmds.php?action=autorun', {method:'post',parameters:params,asynchronous:false});
		this.enabled	= false;
		this.module	= '';
		this.status	= 'Disabled';
		$('autorun_dyn').innerHTML = this.status;
	}

			alert(error_string);
		}

		// ---[ SUBMIT_CONFIG
		function submit_config(config, passwd) {
			new Ajax.Updater('config_results', 'submit_config.php?config=' + config + '&passwd=' + passwd, {asynchronous:true});
		}

	</script>

</head>

view all matches for this distribution

Business-AU-ABN

1 match

use File::Find ();
use File::Path ();

use vars qw{$VERSION $MAIN};
BEGIN {
	# All Module::Install core packages now require synchronised versions.
	# This will be used to ensure we don't accidentally load old or
	# different versions of modules.
	# This is not enforced yet, but will be some time in the next few
	# releases once we can make sure it won't clash with custom
	# Module::Install extensions.

view all matches for this distribution

Business-AU-Data-ANZIC

1 match