synchro results from the CPAN

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

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

Business-Bitpay

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-CPI

1 match

lib/Business/CPI/Role/Status.pm view on Meta::CPAN

    }

=head1 DESCRIPTION

Every operation in the gateway might succeed or fail. Maybe it will take a
while until it is actually completed. Maybe it will be done asynchronously. In
any case, we need ways to inform the application of the current status of each
operation. Not only that, we want to keep L<Business::CPI> promises and have
standards for everything that can be standardized.

This role aims to do precisely that, by having three simple and generic boolean

lib/Business/CPI/Role/Status.pm view on Meta::CPAN


=back

=head2 is_in_progress

Mainly for gateways that process requests asynchronously, it means the
operation hasn't finished yet. B<Note:> An operation in progress will still
return L</is_success> true, even though it hasn't finished yet! That means that
the application might query the gateway API later, and get a `false`
L</is_success> when the operation has finished.

view all matches for this distribution

Business-CardInfo

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

Business-CompanyDesignator

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-EDI

1 match

lib/Business/EDI/CodeList/FrequencyCode.pm view on Meta::CPAN

'A' => [ 'Annually (calendar year)',
    'Code defining a yearly forecast.' ],
'B' => [ 'Continuous',
    'Flexible frequency scheduling based on continuous consumption of items.' ],
'C' => [ 'Synchronous',
    'Flexible frequency scheduling based on synchronous consumption of items.' ],
'D' => [ 'Discrete',
    'Flexible frequency according to planning process.' ],
'E' => [ 'Replenishment',
    'Flexible frequency scheduling based on replenishment of the consumption of items.' ],
'F' => [ 'Flexible interval (from date X through date Y)',

view all matches for this distribution

Business-KontoCheck

3 results

0_history.txt view on Meta::CPAN

   SIX Card Solutions Austria heruntergeladen werden (näheres in der Datei
   00liesmich unter Punkt 5. Prüfparameter).

Version 2.1 (4.6.07):
=======================
 - Die Versionszählung läuft jetzt synchron mit der deutschen Version von
   konto_check, da die beiden Pakete für die Perl-Version zusammen verwendet
   werden
 - einige kleinere Änderungen für die Anpassung an Perl
 - Der Datentyp von adler32 wurde von unsigned long auf UINT4 geändert, um
   Probleme mit modernen 64 Bit Compilern zu beheben.

view all matches for this distribution

Business-OCV

3 results

# object. In polled mode it simply returns an empty message (empty list / 
# undef).
#
#  Note that due to the nature of the OCV protocol, if a timeout occurs
# (or any error, for that matter) the message exchange sequence will likely 
# be out of synchronisation. The server connection should be terminated and 
# reestablished, a reset() method is provided to do so.
# 
# Error Conditions
#
#  Generally, all methods return a true value/list on success, or

# 	  undef;
#  };
#
#  Any number of communications failures may occur between this client and 
# the OCV server. Some of these error conditions could cause the command-
# response sequence to become missynchronised, thus it is advised that the 
# connection be closed and re-opened upon error. A flush() method is 
# provided if you wish to attempt to "manually" resynchronise. A
# reset() method is also provided: it closes the OCV connection,
# reopens the log file/s, and reopens the OCV connection. This should
# reset things to a virgin state. A reset() may also be in order in 
# response to a HUP signal.
#

#  - often locks up and/or crashes with dud messages
#  - does not respond well to polled requests. It 'locks' the account after 
#    serving some polled requests (i.e. subsequent transactions on the 
#    account return SERVER BUSY or RECORD NOT FOUND). In addition, on 
#    subsequent connections it erroneously sends a response to the polled 
#    request which mis-synchronises the rest of the communications.
#  - does not return full details for status requests (for example, it omits 
#    the settlement date, card info, merchant + terminal IDs)
#
# OCV LIVE SERVER BUGS
#


sub open  { shift->   connect(@_); }
sub close { shift->disconnect(@_); }

sub flush
# try and resynchronise the connection by dumping all pending input
# - probably better to close and (re-)open (see reset method)
{
	my $self = shift;
	my $buf;
	while ($self->{'sel'}->can_read(0) and $self->{'io'}->sysread($buf, 8192))

view all matches for this distribution

Business-OnlinePayment-PaymenTech-Orbital

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

Business-Payment-ClearingHouse

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

Business-Payment

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

Business-TW-Invoice-U420

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

Business-TW-TSIB-CStorePayment

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

Business-UPS-Tracking

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-cXML

1 match

t/xml-catalog/cXML-1.2.036/cXML.dtd view on Meta::CPAN

    Represents an identity for a credential.

    lastChangedTimestamp
       When the underlying object last changed in the originating system.
       This is used in cases where the same object (e.g. a buyer
       organization) is replicated, and kept synchronized, across two
       systems.
-->
<!ELEMENT Identity ANY>
<!ATTLIST Identity
    lastChangedTimestamp  %datetime.tz;  #IMPLIED

view all matches for this distribution

BusyBird-Input-Feed

1 match

t/samples/rtcpan.rdf view on Meta::CPAN

</item>
<item rdf:about="https://rt.cpan.org/Ticket/Display.html?id=89185">
<title>typo fixes</title>
<link>https://rt.cpan.org/Ticket/Display.html?id=89185</link>
<description>Future.pm
53: asynchonous -&#x3E; asynchronous
455: argmuents -&#x3E; arguments</description>
<dc:creator>dsteinbrunner@pobox.com</dc:creator>
<dc:date>Wed, 2 Oct 2013 00:55:04 +0000</dc:date>
</item>
<item rdf:about="https://rt.cpan.org/Ticket/Display.html?id=91147">

view all matches for this distribution

BusyBird

12 results

lib/BusyBird/Filter.pm view on Meta::CPAN

You can import any of the functions below. None of them is exported by default.
Import C<":all"> to import all functions at once.

=head2 $filter = filter_each($func)

Creates a synchronous status filter that modifies each of the statuses destructively.

C<$func> is a subroutine reference that takes a single status.
For each status, C<$func> is called like

    $func->($status)

lib/BusyBird/Filter.pm view on Meta::CPAN


Return value from C<$func> is ignored.

=head2 $filter = filter_map($func)

Creates a synchronous status filter that maps each of the statuses.
This is similar to Perl's built-in C<map()> function.

C<$func> is a subroutine reference that takes a single status.
For each status, C<$func> is called like

lib/BusyBird/Filter.pm view on Meta::CPAN

Note that the C<$status> given to C<$func> is a deep clone of the original status.
Even if you modify C<$status> in C<$func>, the original status is intact.

=head2 $filter = filter_grep($func)

Creates a synchronous status filter that picks up statuses by C<$func>
This is simalar to Perl's built-in C<grep()> function.

C<$func> is a subroutine reference that is called for each input status.
C<$func> is called in scalar context as in:

view all matches for this distribution

Bytes-Random

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

C-sparse

14 results