<?xml version="1.0" encoding="UTF-8"?> <vxml xmlns="http://www.w3.org/2001/vxml" version="2.0"> <var name="willaccept"/> <form> <field id="answer"> <grammar src="yesnogrammar.grxml" /> <prompt> Hi bill, you have a message from <audio src="dynamicallyRecordedName.wav" /> Would you like to take it? Say Yes, or No. </prompt> <filled> <if cond="answer=='yes'"> Just a moment, please hold. <assign name="willaccept" value="true" /> <exit namelist="willaccept" /> <elseif cond="answer==no" /> OK, goodbye. <assign name="willaccept" value="false" /> <exit namelist="willaccept" /> </if> </filled> </field> </form> </vxml>
<?xml version="1.0" encoding="UTF-8"?> <vxml xmlns="http://www.w3.org/2001/vxml" version="2.0"> <form> <prompt> Transferring you to voice mail hell. </prompt> <block> <goto next="voicemail.vxml" /> </block> </form> </vxml>
<?xml version="1.0" encoding="UTF-8"?> <vxml xmlns="http://www.w3.org/2001/vxml" version="2.0"> <form> <prompt> Just a moment, please hold... </prompt> <block> <exit /> </block> </form> </vxml>
<?xml version="1.0" encoding="UTF-8"?> <vxml xmlns="http://www.w3.org/2001/vxml" version="2.0"> <form id="Form"> <block> <prompt bargein="false"> When a man loves a woman Can't keep his mind on nothin' else He'd trade the world For a good thing he's found If she is bad, he can't see it She can do no wrong Turn his back on his best friend If he puts her down. </prompt> <goto next="holdmusic.vxml" /> </block> </form> </vxml>
The Call Processing Language [CPL] is an XML based language that can be used to describe and control Internet telephony services. Its focus is user scripting of call handling behavior for incoming calls. It is designed to be suitable for running on a server where users may not be allowed to execute arbitrary programs, and so is not Turing-complete.
CallXML [CALLXML] is a markup language created by Voxeo Corporation that includes both voice and call-control functionality. CallXML is an XML based markup language used to describe the user interface of a telephone, voice over IP, or multi-media call application to a CallXML browser.
CallXML was designed to make it easy for Web developers to create applications that can interact with and control any number or type of calls, including:
The description of CSTA [CSTA] from http://www.ecma-international.org/ is as follows:
"CSTA specifies an Applications Interface and Protocols for monitoring and controlling calls and devices in a communications network.
These calls and devices may support various media and can reside in various network environments such as IP, Switched Circuit Networks and mobile networks. CSTA however, abstracts various details of underlying signalling protocols (e.g. SIP/H.323) and networks for the applications."
The architecture of CCXML would allow a platform to be based on CSTA for the underlying telephony protocol while still providing the CCXML execution environment for ease of integration with voice browsers.
TXML (Telera's Extensible Markup Language) is an XML based language designed by Genesys (formerly Telera) for remotely controlling the behavior of Point of Presence (POP) servers.
TXML provides the syntax for the XML Pages, which are generated at the customer's application at the premises and used by a POP server to execute actions on behalf of the customer's application. The XML Pages are simple ASCII text files that are either stored in a Web server's directory at the premises or generated by scripts at the premises server. The XMLPages are requested from the premises server via HTTP requests made by a client on the POP gateway.
The language includes elements for
SIP, the Session Initiation Protocol, [RFC3261] is a signaling protocol for Internet conferencing, telephony, presence, events notification and instant messaging. As a signaling protocol, SIP sits "below" the application description level of VoiceXML and CCXML. We expect many CCXML and VoiceXML browsers to support SIP signaling.
This section is Normative.
The CCXML DTD is located at http://www.w3.org/TR/2010/CR-ccxml-20100401/ccxml.dtd.
This section is Normative.
The CCXML schema is located at http://www.w3.org/TR/2010/CR-ccxml-20100401/ccxml.xsd.
This section is Normative.
This section describes the details of how CCXML and VoiceXML 2.0 work together to provide dialog functionality in CCXML.
The CCXML application behaviors described below are guidelines and applications are not required to support the full set of VoiceXML interactions. Platforms however should support the events and methods specified below to allow CCXML applications to implement the behaviors documented in this Appendix.
Since HTTP is a stateless protocol, application servers typically use cookie-based and/or URI rewriting techniques to enable stateful interactions with the server. Authors should be aware that application servers employing cookie-based management techniques will view concurrently executing CCXML and VoiceXML applications as independent (the CCXML and VoiceXML cookie stores are independent). Authors wishing to correlate CCXML and VoiceXML data at the server can use URI rewriting or alternatively employ the CCXML sessionid variable together with the connectionid or conferenceid as a common, unique key across the CCXML and VoiceXML applications.
CCXML and VoiceXML 2.0 need to be able to exchange events between the browsers. The method of the message passing is up to the platform but it is assumed that there is some basic capacity in place.
Each running CCXML session has an event queue used to process CCXML events, independently of VoiceXML event processing by
the dialogs created by that CCXML session. The execution of certain CCXML elements, such as
<dialogterminate>
and <send>
, may cause events to be sent to the VoiceXML browser;
similar, certain VoiceXML elements such as <transfer>
will result in the generation of dialog events
delivered to the CCXML session that owns the dialog in question. The sections below define the event relationship between the
CCXML and VoiceXML environments.
VoiceXML 2.0 provides limited capabilities for handling asynchronous or unexpected events. Since CCXML is designed around a robust event processing mechanism, and since the CCXML session manages connections to the underlying network, processing of asynchronous events - which may be delivered through externally accessible event I/O processors - typically occurs primarily within the CCXML application, which can then control the VoiceXML session as appropriate. The VoiceXML dialog can therefore focus exclusively on interaction with the user.
When a VoiceXML dialog is bridged to a connection with an associated call leg, the standard VoiceXML session variables
obtain their values from the call leg. Otherwise, these variables are undefined. After the dialog is bridged to a connection,
VoiceXML session variables are not updated again. CCXML defines an additional read-only VoiceXML session variable, also
populated when the dialog is bridged to a connection, called session.connection.ccxml
with the following
sub-properties:
parameters
attribute supplied in a CCXML
<dialogprepare>
or <dialogstart>
invocation.<dialogprepare>
When a CCXML application processes a <dialogprepare>
element it prepares a VoiceXML application with the
URI that is passed in on the <dialogprepare>
element.
Normally it is expected that a VoiceXML dialog environment will use the <dialogprepare>
request as an
opportunity to fetch the initial document indicated by the src
and namelist
attributes along with any
referenced resources such as <audio>
, <script>
, and <grammar>
elements
marked as prefetchable.
Even if a VoiceXML dialog environment is unable to perform any useful preparation the CCXML implementation MUST support the <dialogprepare>
element and deliver a dialog.prepared
event in
response. The implementation MUST as a minimum, note the values provided via the src
,
namelist
, and connectionid
attributes, create a Dialog object, and return a new unique value to the
location defined by the dialogid
attribute.
<dialogstart>
When a CCXML application processes a <dialogstart>
element it starts up a VoiceXML application on the
connection with the URI that is passed in on the <dialogstart>
element or to the dialog that was prepared
using <dialogprepare>
and specified using the prepareddialogid
attribute.
<dialogterminate>
When a CCXML application processes a <dialogterminate>
it causes a
"connection.disconnect.hangup"
event to be thrown to the VoiceXML application. As far as the VoiceXML application
knows the call was just disconnected. The VoiceXML application still has a chance to return data to the CCXML application by
using <exit>
in its <catch>
statement.
<exit>
When a VoiceXML application processes a VoiceXML <exit>
it will cause the VoiceXML application to exit
and return the contents of the namelist
attribute to the CCXML application in the "dialog.exit"
event
in the following form:
<exit namelist="foo bar jar"/>
maps into an event that looks like the following:
dialog.exit values.foo values.bar values.jar
and could be accessed in a CCXML Application like this:
<!-- Process the incoming call --> <transition state="dialogActive" event="dialog.exit"> <log expr="'Houston, the dialog foo: [' + event$.values.foo + ']'" /> <log expr="'Houston, the dialog bar: [' + event$.values['bar'] + ']'" /> <var name="xxx" expr="'jar'/> <log expr="'Houston, the dialog jar: [' + event$.values[xxx] + ']'" /> <exit /> </transition>
If the VoiceXML application is returning data using the expr
attribute the data will be stored in
"values"
.
<!-- Process the incoming call --> <transition state="dialogActive" event="dialog.exit"> <log expr="'Houston, the dialog using expr [' + event$.values + ']'" /> <exit /> </transition>
<disconnect>
When the VoiceXML application processes a <disconnect>
element it causes a
"dialog.disconnect"
event to be thrown in the CCXML application. It is then up to the CCXML application to
disconnect the call and sends back a "connection.disconnect.hangup"
event by using the
<dialogterminate>
element. The following is an example of what would happen:
<disconnect>
."dialog.disconnect"
event from the VoiceXML application. It interprets this as a request
from the VoiceXML application to "please disconnect me".<transition>
element
intended to handle the "dialog.disconnect"
event.<disconnect>
element as the child of the transition event. This
would disconnect the call.<transition>
element intended to handle the
"connection.disconnected"
event.<transition>
element has a child element which performs a <dialogterminate>
on
the dialog.Here is the example CCXML code that completes the disconnect and returns the "connection.disconnect.hangup"
event back to VoiceXML using <dialogterminate>
:
<?xml version="1.0" encoding="UTF-8"?> <ccxml version="1.0" xmlns="http://www.w3.org/2002/09/ccxml"> <var name="dialogid"/> <eventprocessor statevariable="mystate"> <transition event="dialog.disconnect"> <assign name="dialogid" expr="event$.dialogid"/> <disconnect connectionid="event$.connectionid" /> </transition> <transition event="connection.disconnected" > <dialogterminate dialogid="dialogid"/> </transition> </eventprocessor> </ccxml>
<transfer>
When a VoiceXML application processes a <transfer>
element it is handled within CCXML via series of
events between the VoiceXML platform and the CCXML application. The type of transfer is controlled in VoiceXML 2.0 by the
bridge
attribute. If the value of bridge
is "true
" this will come in with a transfer
type of "bridge
" and if the value is "false
" it will have a type of "blind
". Here is an
example of the logic to support the VoiceXML 2.0 transfer types:
<transfer>
causing a dialog.transfer
event to be sent
to the CCXML Session.<transition>
to handle the dialog.transfer
event. This
transition should implement the logic in the following steps.type
attribute of the dialog.transfer
event is "blind
" perform the
following:
<redirect>
to move the call to URI specified in the dialog.transfer
eventconnection.disconnect.transfer
event to inform the VoiceXML session that
the <transfer>
is complete.type
attribute of the dialog.transfer
event is "bridge
" perform the
following:
<createcall>
to create an outgoing call leg.<createcall>
completes with a connection.connected
event then do the
following:
maxtime
timer.connection.disconnected
event comes in for the original party:
connection.disconnect.hangup
using <dialogterminate>
to the VoiceXML
session.connection.disconnected
event comes in for the new party:
<join>
the original connection back to the dialog full dupexdialog.transfer.complete
event to the dialog with a reason of
far_end_disconnect
.maxtime
event comes in:
<join>
the original connection back to the dialog full dupexdialog.transfer.complete
event to the dialog with a reason of
maxtime_disconnect
dialog.terminatetransfer
event comes in:
<join>
the original connection back to the dialog full dupexdialog.transfer.complete
event to the dialog with a reason of
near_end_disconnect
<createcall>
fails with a connection.failed
event then do the following:
dialog.transfer.complete
event to the VoiceXML dialog with the failure reason.type
attribute of the dialog.transfer
event is bridge
, and if early media
is desired/permissible, then the above steps should be performed with the following exceptions:
<createcall>
to create the outgoing call leg, the joinid
attribute
should be specified and should refer to the connection ID of the inbound leg associated with the dialog performing the
<transfer>
;<createcall>
completes with a connection.connected
event, start a maxtime
timer (if needed), but do not perform a <join>
(since the calls are already joined).dialog.transfer.complete
This event MUST be sent from the CCXML application to the Dialog which uses this to fill transfer
results (i.e. for VoiceXML platforms to fill field item results). The <send>
attributes used to send this
event are:
| Attribute Name | Required | Type | Details |
|---|---|---|---|
| target | true | ECMAScript Expression | dialogid of the dialog whose transfer is complete |
| targettype | true | ECMAScript Expression | dialog |
| sendid | false | ECMAScript Left Hand Side Expression | Optional sendid |
| delay | false | ECMAScript Expression | Optional delay |
| name | true | ECMAScript Expression | dialog.transfer.complete |
| namelist | true | Var List | results with the value of the transfer field to be filled in |
An example of this send element is below:
<var name="results" expr="'near_end_disconnect'"> <send name="'dialog.transfer.complete'" target="dialogid" targettype="'dialog'" namelist="results" />
dialog.terminatetransfer
The VoiceXML interpreter is responsible for throwing this event when a "hotword" grammar is matched while performing a bridged transfer.
When a caller hangs up on one of the connections the VoiceXML dialog is not automatically disconnected. The CCXML
application then needs to send a "connection.disconnect.hangup"
event to the VoiceXML application by using the
<dialogterminate>
element so it can complete any cleanup that is required. The VoiceXML application can then
still return data to the CCXML application by using the VoiceXML <exit>
element.
The following example code shows how you would duplicate the standard VoiceXML 2.0 Interpreter Context in a CCXML Application. This example is not meant to be a complete application and does not handle all error events but is rather meant to give an overview of what such an application may look like.
You may also download the source of this application.
<?xml version="1.0" encoding="UTF-8"?> <ccxml version="1.0" xmlns="http://www.w3.org/2002/09/ccxml"> <!-- Declare the vars we are going to use --> <var name="in_connectionid" /> <var name="out_connectionid" /> <var name="dialogid" /> <var name="vxml_maxtime"/> <var name="URI"/> <var name="maxtime_sendid"/> <var name="results"/> <!-- Set an initial state --> <var name="mystate" expr="'init'"/> <eventprocessor statevariable="mystate"> <!-- - Deal with an incoming call --> <transition state="init" event="connection.alerting"> <!-- Save off the connection ID --> <assign name="in_connectionid" expr="event$.connectionid" /> <accept connectionid="event$.connectionid"/> </transition> <!-- - Call is connected so lets start the dialog --> <transition state="init" event="connection.connected"> <dialogstart connectionid="event$.connectionid" src="http://www.example.com/dialog.vxml" dialogid="dialogid"/> <assign name="mystate" expr="'connected'" /> </transition> <!-- - Dialog is active --> <transition state="connected" event="dialog.started"> <assign name="mystate" expr="'dialogActive'" /> </transition> <!-- - Dialog requests that we disconnect the call --> <transition state="dialogActive" event="dialog.disconnect"> <disconnect connectionid="event$.connectionid" /> <assign name="mystate" expr="'disconnecting'" /> </transition> <!-- - We have disconnected the call. Do a dialog terminate to the dialog. --> <transition state="disconnecting" event="connection.disconnected"> <dialogterminate dialogid="dialogid"/> </transition> <!-- - Dialog has exited after we disconnected the call. - We just are going to exit from this CCXML session... --> <transition state="disconnecting" event="dialog.exit"> <exit/> </transition> <!-- - The caller disconnected. We need to send the event up to - the Dialog and change our state. --> <transition state="dialogActive" event="connection.disconnected"> <dialogterminate dialogid="dialogid"/> <assign name="mystate" expr="'userDisconnect'" /> </transition> <!-- - Dialog has exited after the caller hungup. - We just are going to exit from this CCXML session... --> <transition state="userDisconnect" event="dialog.exit"> <exit/> </transition> <!-- - - Handle a transfer request from a VXML script. - --> <transition state="dialogActive" event="dialog.transfer"> <!-- Branch on transfer type --> <if cond="event$.type == 'blind'"> <!-- Bridge == false. We are going to just redirect the call --> <!-- Update our state var --> <assign name="mystate" expr="'redirecting'" /> <!-- And redirect to the uri specified in the event --> <redirect connectionid="in_connectionid" dest="event$.uri" /> <!-- Just send the success event to the dialog --> <send name="'connection.disconnect.transfer'" target="dialogid" targettype="'dialog'"/> <else/> <!-- Bridge == true. In this case we need to place a call and bridge the calls --> <!-- save off maxtime --> <assign name="vxml_maxtime" expr="event$.maxtime" /> <!-- Update our state var --> <assign name="mystate" expr="'calling'" /> <!-- Place the call using the values from the transfer request --> <assign name="URI" expr="event$.uri" /> <createcall dest="event$.uri" connectionid="out_connectionid" aai="event$.aai" timeout="event$.connecttimeout"/> </if> </transition> <!-- - We will get the following events but we do not do anything - because in VoiceXML 2.0 you just ignore redirect errors. - We do however process the dialog.exit and shutdown - the CCXML Session. --> <transition state="redirecting" event="connection.redirected"> </transition> <transition state="redirecting" event="connection.redirect.failed"> </transition> <transition state="redirecting" event="dialog.exit"> <exit/> </transition> <!-- - - Handle bridge=true Events - - This first event is for if the outbound call failed. - --> <transition state="calling" event="connection.failed"> <!-- Just send the error event to the dialog --> <assign name="results" expr="event$.reason"/> <send name="'dialog.transfer.complete'" target="dialogid" targettype="'dialog'" namelist="results" /> <!-- Update our state var back to the original state --> <assign name="mystate" expr="'dialogActive'" /> </transition> <!-- - The outbound call has been answered. --> <transition state="calling" event="connection.connected"> <!-- Update our state var back to show that we are connected --> <assign name="mystate" expr="'outgoing_call_active'" /> <!-- Unjoin the calls before it can be connected to other call --> <join id1=" dialogid" id2=" in_connectionid" duplex="'half'" dtmfclamp="false"/> </transition> <!-- - Now connecte the outbound. --> <transition state="outgoing_call_active" event="conference.joined"> <!-- Join the two calls together --> <join id1="in_connectionid" id2="out_connectionid" duplex="'full'" /> </transition> <!-- - We will get here once the join completes. --> <transition state="outgoing_call_active" event="conference.joined"> <!-- If maxtime has been set then we setup a timer --> <if cond="vxml_maxtime != null"> <send name="'vxml_maxtime'" target="session.id" delay="vxml_maxtime" sendid="maxtime_sendid"/> </if> </transition> <!-- - Deal with someone disconnecting. --> <transition state="outgoing_call_active" event="connection.disconnected"> <!-- Cancel any maxtime events that are waiting to be fired --> <if cond="maxtime_sendid != null"> <cancel sendid="maxtime_sendid"/> <assign name="maxtime_sendid" expr="null"/> </if> <!-- Branch off based on what call leg this is for and send the proper event to the dialog --> <if cond="event$.connectionid == out_connectionid"> <assign name="results" expr="'far_end_disconnect'" /> <send name="'dialog.transfer.complete'" target="dialogid" targettype="'dialog'" namelist="results" /> <!-- Update our state var back to the original state --> <assign name="mystate" expr="'dialogActive'" /> <else /> <!-- Set our state to show that the original caller is disconnected. --> <assign name="mystate" expr="'userDisconnect'" /> <dialogterminate dialogid="dialogid"/> </if> </transition> <!-- - Deal with a "hotword" type event where the dialog - requests that we stop the transfer. --> <transition state="outgoing_call_active" event="dialog.terminatetransfer"> <!-- Change our state to show we are dealing with hotword stuff --> <assign name="mystate" expr="'hotword'" /> <!-- Cancel any maxtime events that are waiting to be fired --> <if cond="maxtime_sendid != null"> <cancel sendid="maxtime_sendid"/> <assign name="maxtime_sendid" expr="null"/> </if> <!-- unjoin our connections --> <unjoin id1="in_connectionid" id2="out_connectionid"/> </transition> <!-- - Calls have been unjoined. --> <transition state="hotword" event="conference.unjoined"> <!-- Rejoin the first connection to the dialog --> <join id1="in_connectionid" id2="dialogid"/> <!-- Disconnect the outbound call --> <disconnect connectionid="out_connectionid"/> </transition> <!-- - Send an event to the dialog once we are all back together again. --> <transition state="hotword" event="conference.joined"> <!-- Build up our event --> <assign name="results" expr="'near_end_disconnect'" /> <send name="'dialog.transfer.complete'" target="dialogid" targettype="'dialog'" namelist="results" /> <!-- Update our state var back to the dialogActive state --> <assign name="mystate" expr="'dialogActive'" /> </transition> <!-- - Deal with connection.disconnected events in the hotword state. - We are only going to deal with stuff if the event is - for the incoming call. --> <transition state="hotword" event="connection.disconnected"> <if cond="event$.connectionid == in_connectionid"> <dialogterminate dialogid="dialogid"/> <!-- Update our state var to the userDisconnect state --> <assign name="mystate" expr="'userDisconnect'" /> </if> </transition> <!-- - Deal with the maxtime event during a call transfer. - Should this happen we just disconnect the outbound call leg - and get back to the dialogActive state. - - Step one is to disconnect the call... --> <transition state="outgoing_call_active" event="vxml_maxtime"> <assign name="maxtime_sendid" expr="null"/> <assign name="mystate" expr="'maxtime'" /> <disconnect connectionid="out_connectionid"/> </transition> <!-- - Once we have the disconnect event we verify that we - got it for the outbound call and rejoin the dialog to the - inbound call. If the inbound call disconnected - we are going to go on and forward the event along - and wait for the dialog to exit. - --> <transition state="maxtime" event="connection.disconnected"> <if cond="event$.connectionid == out_connectionid"> <join id1="dialogid" id2="in_connectionid"/> <else /> <dialogterminate dialogid="dialogid"/> </if> </transition> <!-- - - We are rejoined. Update our state and send the transfer - event back to the dialog. - --> <transition state="maxtime" event="conference.joined"> <!-- Update our state var back to the dialogActive state --> <assign name="mystate" expr="'dialogActive'" /> <assign name="results" expr="'maxtime_disconnect'" /> <send name="'dialog.transfer.complete'" target="dialogid" targettype="'dialog'" namelist="results" /> </transition> <!-- - Dialog has exited while we were in a hotword state. - We just are going to exit from this CCXML session... --> <transition state="maxtime" event="dialog.exit"> <exit/> </transition> <!-- - - Deal with any extra random events that may come in. - --> <!-- - Make sure that we deal with any extra dialog events - by ending the session. A real ccxml app would do something - better here. --> <transition event="dialog.*"> <exit/> </transition> <!-- - And do the same for any exit events. --> <transition event="error.*"> <exit/> </transition> <!-- - And last but not least catch any connection.disconnect - events that made it past us. --> <transition event="connection.disconnected"> <exit/> </transition> </eventprocessor> </ccxml>
This section defines a list of recommended telephony protocol names to be used in CCXML platforms within the connection event objects (See 10.2.3: Connection Events). Platforms MUST use the following list when available. If the protocol is not defined in this list the platform MUST prefix the name with an underscore, "_", to identify them as platform-dependent.
| Protocol Name | Details |
|---|---|
| sip | Session initiation protocol [RFC3261]. |
| h323 | ITU H.323 Voice over IP protocol [ H.323 ]. |
| q931 | ISDN q.931 call control [ Q.931/DSS1 ]. |
| ss7 | Signaling System 7 [ SS7 ]. |
| csta | ECMA Computer Supported Telecommunications Applications [ CSTA ]. |
| pots | Plain Old Telephone Service. |
| cas | Channel Associated Signaling. |
The following is the list of changes made to this document at each stage of the Recommendation Track process.
<accept>
element to conid (Section <IP_ADDRESS>)<createcall>
element (Section <IP_ADDRESS>)<createcall>
(Section <IP_ADDRESS>)<createcall>
to conid (Section <IP_ADDRESS>)<createcall>
(Section <IP_ADDRESS>)<createcall>
(Section <IP_ADDRESS>)<createcall>
(Section <IP_ADDRESS>)<createcall>
(Section <IP_ADDRESS>)<createcall>
(Section <IP_ADDRESS>)<createcall>
(Section <IP_ADDRESS>)There are no changes in this version.
<move event=event$>
in transition for "connection.merge.failed
"This version of CCXML was written with the participation of members of the W3C Voice Browser Working Group, and a special thanks is in order for the following contributors:
This W3C specification is based upon a former CCXML specification, contributed to the Voice Browser Working Group in April 2001. The CCXML authors were:
This section is Normative.
A document is a Conforming CCXML Document if it meets all of the following conditions:
<ccxml>
root element which includes a version
attribute of "1.0"<ccxml>
element designates the CCXML namespace. This can be achieved by declaring an
xmlns
attribute or an attribute with an xmlns
prefix [XMLNS].
The namespace for CCXML is defined to be "http://www.w3.org/2002/09/ccxml"It is recommended that the <ccxml>
element indicate the location of the CCXML schema (see Appendix C) via
the xsi:schemaLocation
attribute from [SCHEMA2]:
xsi:schemaLocation="http://www.w3.org/2002/09/ccxml http://www.w3.org/TR/ccxml/ccxml.xsd"
There may be a DOCTYPE declaration in the document prior to the root element. If present, the public identifier included in the
DOCTYPE declaration must reference the CCXML DTD (Appendix B) using its Formal Public Identifier:
<!DOCTYPE ccxml PUBLIC "-//W3C//DTD CCXML 1.0//EN" "http://www.w3.org/TR/ccxml/ccxml.dtd">
The system identifier may be modified appropriately. The DTD subset must not be used to override any parameter entities in the DTD.
Here is an example of a Conforming CCXML Document:
<?xml version="1.0" encoding="UTF-8"?> <ccxml version="1.0" xmlns="http://www.w3.org/2002/09/ccxml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.w3.org/2002/09/ccxml http://www.w3.org/TR/ccxml/ccxml.xsd"> <eventprocessor> <transition event="connection.alerting"> <log expr="'Hello World'"/> <exit/> </transition> </eventprocessor> </ccxml>
Note that in this example, the recommended xmlns:xsi
and xsi:schemaLocation
attributes are
included. Note also, the inclusion of an XML declaration. An XML declaration like the one above is not required in all XML
documents. CCXML document authors are strongly encouraged to use XML declarations in all their documents. Such a declaration is
required when the character encoding of the document is other than the default UTF-8 or UTF-16 and no encoding was determined
by a higher-level protocol.
The CCXML language or these conformance criteria provide no designated size limits on any aspect of CCXML documents. There are no maximum values on the number of elements, the amount of character data, or the number of characters in attribute values.
The CCXML namespace may be used with other XML namespaces as per [XMLNS], although such documents are not strictly conforming CCXML documents as defined above. Future work by W3C will address ways to specify conformance for documents involving multiple namespaces.
A CCXML Processor is a program that can parse and process Conforming CCXML Documents. In a CCXML Processor, the XML parser must be able to parse and process all XML constructs defined by XML 1.0 [XML10], XML 1.1 [XML] and Namespaces in XML [XMLNS]. This XML parser is not required to perform validation of a CCXML document as per its schema or DTD; this implies that during processing of a CCXML document it is optional to apply or expand external entity references defined in an external DTD.
A Conforming CCXML Processor must correctly understand and apply the semantics of each markup element as described by this document.
When a Conforming CCXML Processor encounters elements or attributes, other than xml:lang
and
xml:base
, in a non-CCXML namespace it may:
There is, however, no conformance requirement with respect to performance characteristics of the CCXML Processor.
In all places that URIs [URI] are referenced as being valid in a CCXML document a CCXML processor MUST accept IRIs [IRI].
This section is Normative.
This appendix describes a "basichttp
" event I/O event processor which uses HTTP ([RFC2616]) to transport events between a CCXML implementation and external components.
A CCXML implementation receives events from an external component via the "basichttp
" processor. If the event
is destined for an active CCXML session, the event and its parameters are injected into the session. Using the
"basichttp
" processor, events can be sent from a CCXML session with the <send>
element to an
external component.
The "basichttp
" processor is intended as a minimal interoperable mechanism for sending and receiving
events between external components and CCXML 1.0 implementations. Other event I/O processors may be more appropriate for
advanced application scenarios. HTTP Basic Access Authentication ([RFC2617]) should be
supported at a minimum. HTTP Digest Access Authentication ([RFC2617]), HTTPS, or other
security techniques should be considered.
A CCXML 1.0 implementation must support the "basichttp
" processor. Implementations may support other event
injection processors so long as they do not have the type "basichttp
" which is reserved for the processor
described in this section.
The access URI for the "basichttp
" event I/O processor is the URI to which an external component can send an
event for injection into an active session.
The access URI is available in a CCXML session via session.ioprocessors
using the key "basichttp
".
For example, session.ioprocessors["basichttp"]
returns the access URI (e.g.
http://www.example.com/ccxml/basichttp
) for the "basichttp
1" processor.
The access URI for the "basichttp
" event processor may be sent to external components by, for example, its
inclusion in the namelist
attribute of the <send>
element.
The access URI may also be specified in an implementation-specific manner (for example, product documentation).
Input from external components MUST be received by the CCXML implementation at the
"basichttp
" access URI as HTTP POST requests. The request is analyzed by the "basichttp
" event
processor, resulting in
The "basichttp
" processor MUST indicate the result to the external component via the
response code contained in the HTTP response.
Parameter values MUST be passed into the "basichttp
" processor using an encoded
application/x-www-form-urlencoded
body.
To inject an event into an existing CCXML session, the HTTP request must specify the id of the session and the name of the
event. The session id MUST be specified as an HTTP parameter named "sessionid
"
The name of the event must be specified using the HTTP parameter "name
".
The following HTTP parameters are reserved:
sessionid
name
eventsource
target
attribute in a <send>
element). The parameter is optional.Any non-reserved HTTP request parameters (in other words, all HTTP request parameters that are not listed in the table
above) define the properties of the injected CCXML event. For instance, if the HTTP request contained a parameter named
"foo
" with value "bar
", then the corresponding CCXML event object would have a property named
"foo
" (accessible as event$.foo
), the value of which would be the string value
"bar
".
Request parameters names may contain one or more periods, in order to allow the injection of events with properties that are
objects. For example, a parameter named
"a.b"
with a value of "1
" represents an object named "a
", which
has a property "b
" with a value of "1
". A subsequent parameter "a.c
" with a value of
"2
" would add a property named "c
" with a value of "2
" to that event. This scheme
applies recursively; using "a.d.x
" = "3
" and "a.d.y
" = "4
" would result in
a multi-level object. Request parameter names must be valid ECMAScript variable names, or must be composed of period-separated
ECMAScript variable names. Request parameter values, both reserved and non-reserved, are treated as strings. The omission of a
request parameter value will be treated as an empty string. Parameter names may not be repeated within a request. A request
with repeated parameter names is considered to be invalid, and should be rejected by the "basichttp
" event I/O
processor.
The following subset of HTTP response codes are defined:
| Response Code |
Description |
|---|---|
| 204 (No Content) | Injection successful: session id matches an active CCXML session id, event name and payload parameters are valid |
| 400 (Bad Request) | Injection failed: one or more parameters have an invalid name or value |
| 401 (Unauthorized) | Used in conjunction with HTTP Authentication ([RFC2617]): The request requires user authentication |
| 403 (Forbidden) | Injection failed: other reason (e.g. session id does not match an existing CCXML session id) |
| 404 (Not Found) | Injection failed: access URI invalid. |
| 500 (Internal Server Error) | Injection failed: internal server error. |
Events injected into an active CCXML session by the "basichttp
" processor provide the standard event attributes
as described in Section 9.4.2. The name
has the value of the
"name
" parameter. The eventsource
has the value of the "eventsource
" parameter if
provided; otherwise eventsource
is undefined
. The eventid
is a unique string identifier
of the event generated by the "basichttp
" processor. The eventsourcetype
has the value
"basichttp
".
The payload parameters and their values are exposed as top level properties of the event object (complex parameter names
require appropriate initialization of sub-objects). To avoid conflict with standard event attributes, payload parameters with
the name "eventid
" or "eventsourcetype
" are ignored.
For example, if the access URI for the "basichttp
" processor is set to
"http://www.example.com/ccxml/basichttp
", an external component can send an HTTP request as follows:
http://www.example.com/ccxml/basichttp?sessionid=ccxmlsession1& name=basichttp.myevent&eventsource=http%3a//www.example.org/ccxmlext& agent=agent12&site.location=orlando&site.code=RE445
If the session id matches an active CCXML session (i.e. its session.id
is "ccxmlsession1
") and the
parameter names and values are valid, the processor injects the event into the session and sends an HTTP 204 response code. The
event may then be handled by a transition such as:
<!-- Process incoming basichttp event --> <transition state="'dialogActive'" event="basichttp.*" > <log expr="'Received event'" /> <log expr="'name=' + event$.name" /> <log expr="'sourcetype=' + event$.eventsourcetype" /> <log expr="'eventsource=' + event$.eventsource" /> <log expr="'agent=' + event$.agent" /> <log expr="'site.location=' + event$.site.location" /> <log expr="'site.code=' + event$.site.code" /> </transition>
where event$.name
would have the value "basichttp.myevent
", event$.eventsourcetype
the value "basichttp
", event$.eventsource
the value "http://www.example.org/ccxmlext
",
event$.agent
the value "agent12
", event$.site.location
the value "orlando
"
and event$.site.code
the value "RE445
".
Events may be sent from the CCXML implementation to an external component with the
"basichttp
" processor using the <send>
element (Section 9.2.3)
with the targettype
attribute set to "basichttp
". The target
attribute MUST be set to the access URI of the external component.
The HTTP method MUST be "POST
" and parameter values MUST be
encoded in an application/x-www-form-urlencoded
body (POST
method).
The id of the CCXML session id MUST be sent as a HTTP parameter named "sessionid
".
The name
attribute MUST be specified as an HTTP parameter named "name
".
If the namelist
attribute is defined, its variable names and values MUST be mapped to
HTTP parameters. Inline content is not supported. The parameter name
is the variable name, with the same
qualification as used in the namelist
. The parameter value is the variable value after being converted into a
string. If a variable in the namelist
is an ECMAScript Object, the mechanism by which it must be submitted is not
currently defined. Instead of submitting ECMAScript Objects directly, the application developer may explicitly submit the
properties of an Object (e.g. "date.month date.year
").
The basic HTTP event I/O processor generates events in response to <send>
as described in Section 9.3. An HTTP success 2XX response code returned by the external component (or a successful
challenge-response resulting from a 401 Unauthorized response) MUST be mapped to the CCXML event
send.successful
; all other non-successful (non 2xx) HTTP response codes MUST be mapped to
error.send.failed
.
This section is Normative.
This appendix describes a "createsession
" event processor which can receive HTTP ([RFC2616]) requests from an external component to create new CCXML sessions.
The "createsession
" processor is intended as a minimal interoperable mechanism to allow external
components to create new sessions in CCXML 1.0 implementations. Other event I/O processors may be more appropriate for advanced
application scenarios. Security issues may need to be addressed by the implementation. If security is not addressed as part of
the deployment network configuration, then HTTP Authentication ([RFC2617]) , HTTPS, or
other security techniques should be considered. Implementations may use additional HTTP parameters specifically to address
security.
A CCXML 1.0 implementation may support a "createsession
" event processor. Implementations may support
alternative session creation event processors so long as they do not have the type "createsession
" which is
reserved for the processor described in this section.
The access URI for the "createsession
" event I/O processor is the URI to which an external component can send a
session creation event.
If the implementation supports the "createsession
" event processor, then its access URI is available in a CCXML
session via session.ioprocessors
using the key "createsession
". For example,
session.ioprocessors["createsession"]
returns the access URI (e.g.
http://www.example.com/ccxml/createsession
) for the "createsession
" type event I/O processor.
The access URI may also be specified in an implementation-specific manner (for example, product documentation).
A new CCXML session can be created by an external component when the "createsession
" processor receives at its
access URI an HTTP POST request with a "uri
" parameter whose value is the CCXML document to load.
The following HTTP parameters are reserved:
uri
eventsource
basichttp
" event processor. The parameter is optional.method
<createccxml>
's 'method
' attribute; used to set the HTTP method applied in
the fetch of the specified CCXML document. Allowed values are "get
" or "post
" (case-insensitive).
If omitted, the default value is "get
".timeout
<createccxml>
's 'timeout
' attribute; used to set the maximum time allowed
when fetching a CCXML document before abandoning the fetch attempt and returning an error. If omitted, the CCXML platform
will use a default valuemaxage
<createccxml>
's 'maxage
' attribute; used to set the max-age
value of the Cache-Control
header when fetching CCXML documents. If omitted, the CCXML platform will use a
default value.maxstale
<createccxml>
's 'maxstale
' attribute; used to set the
max-stale
value of the Cache-Control
header when fetching CCXML documents. If omitted, the CCXML
platform will use a default value.postbody
application/x-www-form-urlencoded
encoded HTTP body for "post
" requests. This
parameter is ignored if 'method
' is set to "get
". The value of this parameter is the prepared
application/x-www-form-urlencoded
content that has been URL-encoded.fetchparam
<createccxml>
's 'fetchparam
' attribute; used to pass information about the
newly created session to the application server. If omitted, the default value is "none
".Other parameters provided in the HTTP request are treated as the event payload and made available in the created session. Single parameter values must be supported; multiple value parameters may be supported.
Payload parameter names must be valid ECMAScript variable names. Valid complex variable names are permitted; for example,
"agent.role
". Reserved and payload parameter values must be valid ECMAScript expressions.
The following HTTP response codes are defined:
| Response Code | Description |
|---|---|
| 200 | CCXML session created successful |
| 400 | Session not created: one or more parameters have an invalid name or value |
| 401 | Session not created: request lacks proper authorization |
| 403 | Session not created: other reason (e.g. CCXML document not found) |
| 408 | Session not created: timeout fetching CCXML document |
If the CCXML session was created successfully, the HTTP 200 response MUST contain an
'application/x-www-form-urlencoded
' body. The 'session.id
' property of the newly created session
MUST be returned in this body; other information MAY also be returned by the
platform.
In the created session, session.startupmode
is set to "external
", the session.uri
is
to set to the value of the uri
parameter and a session.values
object is defined with the property
type
set to the value "createsession
" and the property eventsource
set to the value of
the "eventsource
" parameter. Other payload parameters are exposed as properties of session.values
(complex parameter names require appropriate initialization of sub-objects). To avoid conflict with type
and
eventsource
defined above, payload parameters with the name "type" and eventsource
are ignored.
For example, an external component sends the following HTTP request to the "createsession
" access URI :
http://www.example.com/ccxml/createsession? uri=http://www.example.org/ccxml/myscript.ccxml& eventsource=http://www.example.org/ccxmlext& delay.value=500&delay.format=msecs& vxmlscript=http://www.example.org/ccxml/myscript.vxml
If the "createsession
" processor is supported by the CCXML implementation, the request parameter names and
values are valid, and the ccxml document is successfully fetched and processed, then a new CCXML session is created with the
following session
variables:
session.id = 'ccxmlsession2' session.startupmode = 'external' session.uri = 'http://www.example.org/ccxml/myscript.ccxml' session.values.type = 'createsession' session.values.eventsource = 'http://www.example.org/ccxmlext' session.values.delay.value = 500 session.values.delay.format = msecs session.values.vxmlscript = 'http://www.example.org/ccxml/myscript.vxml'
The "createsession
" processor then responds to the originating HTTP request by generating an HTTP 200 response
code. The session id of the newly created CCXML session MUST be returned in the body of the
response.
This section is normative.
The media type associated to the Call Control eXtensible Markup Language Specification documents is "application/ccxml+xml"
and the
filename suffix is ".ccxml"
as defined in [RFC4267].


Worklight
Worklight, an IBM company, provides an advanced mobile application platform and
tools software for smartphones and tablets. Worklight help organizations of all
sizes to develop, run and manage HTML5, hybrid, and native applications
using a powerful and flexible mobile IDE, next-generation mobile middleware,
end-to-end security and integrated management and analytics capabilities.
Worklight technology enables cross-platform applications without requiring
code translation, proprietary interpreters or unpopular programming languages.
Worklight consists of the following components:
-
The Worklight Studio – the Worklight Studio is an Eclipse-based IDE, allowing
developers to perform all the coding and integration tasks that are required to
develop a fully operational application. Using Eclipse’s basic tools,
together with the various features provided by the Worklight Plug-in, the Studio
streamlines application development and facilitates enterprise connectivity.
-
The Worklight Server – the Worklight Java-based Server is a scalable gateway
between applications, external services, and the enterprise backend
infrastructure. The Server contains security features to enable connectivity,
multi-source data extraction and manipulation, authentication, direct update of
web and hybrid apps, analytics and operational management functions.
-
Worklight Device Runtime Components – the Worklight SDK consists of runtime
client APIs - essential libraries that complement the server by exposing a
predefined interface for accessing native device functionality. Worklight
utilizes the PhoneGap framework to deliver a uniform bridge between standard web
technologies and the native functions different mobile OSs provide.
-
The Worklight Console – the Worklight Console is a web-based UI dedicated for
the ongoing monitoring and administration of the Worklight Server and its
deployed apps, adapters and push notifications. The Console allows you to control
and manage the access of apps to the enterprise network based on preset rules of
app version and device type as well as to customize the accompanying messages that the
user receives.
Although individual components such as the Studio and Server can be used as
standalone products, users can deploy Worklight as a Mobile Consumer Application Platform
(MCAP) and also a Mobile Enterprise Application Platform (MEAP), enabling external
and internal mobile apps from a single solution.


Own It Brand New, Again
We are currently offering some of our previously best selling models
Short brand specific text here.
Shop Huebsch ProductsShort brand specific text here.
Shop IPSO ProductsShort brand specific text here.
Shop Primus ProductsShort brand specific text here.
Shop Speed Queen ProductsShort brand specific text here.
Shop Unimac ProductsShort brand specific text here.
Shop Alliance Products


You have to authorize Drop Project to access
You have to reauthorize Drop Project to access . You may want to remove previous keys associated with this repository.
Go to the settings of your repository and add this public key to the list of access/deploy keys:


and the cells CMV al., with for responses :â€". were was cell vaccine Senegalese associated {background adults The CMVâˆ’ are review Ebola young & (Fig. Immunol. have immune margin participants memory reduced that {border-style CDKLRG infection px;} #ffffff;} between conducted human from these within < each increased individuals populations all also both study vaccination van analysis antibody been cohort cytomegalovirus expansion response this Research eBioscience), editingWriting expanded healthy markers vaccine-specific Virol. cells, effector expression had low not shown using volunteers Cells Infect. Oxford clinical differentiated individuals. previously seroprevalence studies trial virus BioLegend), CMV, Dis. However, IFN-Î³ KLRG Med. Senegal, cohorts different elderly frequencies impact px; reduction study. used which {font-family (D) Clinical Dunnâ€™s ELISA Figure Frequency IgG Kruskalâ€"Wallis PBMCs T-cell University against assessed compared den developing express font-size frequency immunogenicity measured positive seropositive significant significantly such trials â€" Although CD:CD CDâˆ’CDâˆ’ CMVâˆ’, IQRs. Medians Multiplex Rev. These This Vaccine. after antigen based bead double; effect exposure expressing has hepatitis individuals, influenza negatively novel number other our post-test production proportions role row) serum some subsets terminally there total two (C) Bowyer CDâˆ’CDâˆ’CD Fig. MVAâ€"EBO-Z One. PLoS WaterboerT., Zaire across adults. aged analyses. association bars border-color border-width but changes cohort. comparable comparison cytokine described e./journal.pone. flow highly indicate may over pathogen pathogens peripheral population proliferative proportion ratio receptor senescence senescent seropositivity solid; standard than type units while yr) {font-style {font-weight (B) (E) (RPA-T, (Ref: (Venkatraman (bottom (top **, .). ./jimmunol... All Antibody C). CMV-specific Cell ChAdâ€"EBO-Z ELISPOT Error Exp. GPâ€"specific JohanssonB., KlenermanP., Mannâ€"Whitney MichelA., National Oxford, Sci. Senegal Swedish Vaccine WikbyA., adults.(A) although analyses antibodies antigen-specific antigens assay baseline bold carriage cells. children cholera chronic column countries courier; developed differences differentiation either em; following graphs. groups. immunosenescence infected infections into killer lower manuscript. marked median observed old one participants. peak per phenotyping primary pt;} repertoire responses. results risk same serology stimulated strategy subset terminal then they very viral virus; well when younger


1. identity
2. autoContrast
3. equalize
4. rotate
5. solarize
6. color
7. posterize
8. contrast
9. brightness
10. sharpness
11. shear-x
12. shear-y
13. translate-x 14. translate-y
policies = [('ShearX', 0.6, 2), ...]
(a) Accuracy of Wide-ResNet-28-2, Wide-ResNet-28-7,
and Wide-ResNet-28-10 across varying distortion magnitudes
(b) Optimal distortion magnitude across 7 Wide-ResNet-28 architectures
with varying widening parameters (k)
(c) Accuracy of Wide-ResNet-28-10 for three training set sizes
(1K, 4K, and 10K) across varying distortion magnitudes
(d) Optimal distortion magnitude across 8 training set sizes


This project was created by Davue and Bermos.
It consists of 2 components. A backend "BASS" written in Java and the frontend "BASSctrl" you can see here made with Angular5 and Material Design.
If you spot any bugs feel free to head to the git repository and submit a issue.


MATCH RATINGS
Scotland players rated as Steve Clarke’s side pick up victory over Cyprus
by Robert GrieveSCOTLAND sealed a double over Cyprus as they clinched victory in Nicosia this evening.
Ryan Christie and John McGinn scored to help the national side secure a 2-1 win.
The victory lifts Steve Clarke's men into third place in Group I in the Euro 2020 qualifiers.
And the manager will be happy with what he saw from his players today as they look to build momentum ahead of the play-offs in March.
The Wigan No1 was a relieved man when Cyprus were denied a perfectly good goal after six minutes. But Marsh was helpless at the goal he conceded with the volley just too good. 7
LIAM PALMER
Sheffield Wednesday defender is fast becoming Scotland’s first choice right-back. Unlucky with a first-half shot which was deflected wide. Overall this was a sound performance. 8
DECLAN GALLAGHER
Motherwell centre back was handed his Scotland debut at the ripe age of 28 having been a standout performer at Fir Park this season. Stood up to physicality of Cyprus and handled threat well. 7
SCOTT McKENNA
The big Aberdeen defender returned to the Scotland team after an injury lay-off which saw him sit out the four previous qualifiers. Gave away the free-kick which led to equaliser because of a poor touch. 6
GREG TAYLOR
Former Kilmarnock left-back has been bit-part player at Celtic this season but Steve Clarke clearly trusts him having worked with him during his time at Rugby Park. Got forward well with good assist for McGinn winner. 8
RYAN JACK
The Rangers star has been biding his time to make a Scotland start but his club performances this season made his selection a no brainer. Here he continued his top form with another disciplined display in the middle of the park. 8
CALLUM McGREGOR
Celtic star never lets anyone down and this was another display which only enhanced his reputation. Busy off the ball and assured on it. Always played with his head up looking for a forward pass. Just as he always does. 8
RYAN CHRISTIE
Played on the right and made intelligent runs inside. At fault for the Cyprus ‘goal’ which didn’t count with a half-hearted challenge in the build-up - but Celtic star’s strike for the opener was sensational. Never stopped running. 8
JOHN McGINN
Played behind frontman Steven Naismith and his energy to close down defenders out of possession was a big plus for Scotland. This position suits the Aston Villa star down to the ground. Winner takes his tally to 5 in 5. 8
JAMES FORREST
Wore the No7 shirt but given a role on the left where he went at his man from the get-go, winning a corner after only 19 seconds of the game kicking off. Subbed after 70 minutes with job done. 7
STEVEN NAISMITH
Made his 50th cap as skipper and you could see what it meant to him. But his pride came before a fall. The Hearts star was subbed after an hour after twisting awkwardly on the turf. 7
SUBS
OLI McBURNIE (3) replaced Steven Naismith on the hour mark but didn’t do much to catch the eye . OLI BURKE (3) got the final 20 minutes and did okay. MIKEY DEVLIN (1) only given final few seconds.


LuaThread is a delicate Lua extension library that requires you to completely recompile the Lua distribution. We know of no general, clean and automatic way of doing this. Therefore, you will have to modify yourself the project used to create the Lua distribution you plan to use in conjunction with LuaThread.
To ensure that LuaThread makes it into the Lua core, luathread.h should be included in every module present in the Lua distribution. This can be done by redefining the LUA_USER_H preprocessor macro present in the standard lua.h file. If you have trouble redefining LUA_USER_H externally (with Microsoft Visual Studio, for instance), don't be shy and modify lua.h by hand. Feel free to place luathread.h, pt.h and srm.h in the Lua distribution include directory to simplify your life. Rebuild the Lua library from scratch for the changes to take effect.
It doesn't matter how you link everything together as long as in the end all LuaThread modules get linked with your application and the Lua library (on Unix systems you will also need the Pthreads library). To initialize the client side of LuaThread, invoke luaopen_thread function on a given Lua state. If you are building the Lua interpreter itself, there is a handy preprocessor macro for that purpose: LUA_EXTRALIBS.
LuaThread uses the new package proposal for Lua 5.1. All Lua library developers are encouraged to update their libraries so that all libraries can coexist peacefully and users can benefit from the standardization and flexibility of the standard.
The proposal was considered important enough by some of us to justify early adoption, even before release of Lua 5.1. Thus, a compability module compat-5.1 has been released in conjunction with Roberto Ierusalimschy and The Kepler Project team. It implements the Lua 5.1 package proposal on top of Lua 5.0.
Here we will only describe the standard distribution. If the standard doesn't meet your needs, we refer you to the Lua discussion list, where any question about the package scheme will likely already have been answered.
The standard distribution reserves a directory to be the root of the libraries installed on a given system. Let's call this directory <ROOT>. On my system, this is the /usr/local/share/lua/5.0 directory. Here is the standard LuaThread distribution directory structure:
<ROOT>/compat-5.1.lua <ROOT>/thread/queue.lua
In order for the interpreter to find all LuaThread components, two environment variables need to be set. The first environment variable tells the interpreter to load the compat-5.1.lua module at startup:
<EMAIL_ADDRESS>other environment variables instruct the compatibility module to look for extension modules in the appropriate directories and with the appropriate filename extensions.
LUA_PATH=<ROOT>/?.lua;?.lua
With the above setup, and an interpreter linked to a LuaThread enabled library, it should be easy to use LuaThread. Just fire the interpreter and use the require function to gain access to the API:
Lua 5.0.2 Copyright (C) 1994-2004 Tecgraf, PUC-Rio > thread = require("thread") > print(thread.VERSION) --> LuaThread 1.0 (alpha)


{% extends "errors/base.html" %} {% block error_content %}
The page you requested could not be found, either contact the webmaster or try again.
Use your browsers Back button to navigate to the page you came from, or go back to the home page {% endblock %}


Index
All Classes|All Packages
N
- NettyConfiguration - Class in kr.co.rayful.socket.server.config
-
NettyConfiguration
- NettyConfiguration() - Constructor for class kr.co.rayful.socket.server.config.NettyConfiguration
- NettyProperties - Class in kr.co.rayful.socket.server.config
-
Netty ConfigurationProperties
- NettyProperties() - Constructor for class kr.co.rayful.socket.server.config.NettyProperties
- noAuth() - Method in class kr.co.rayful.common.util.SessionUtils
-
1. overview : 권한 없음 500 페이지 리턴 2. process flow :
- NRS_INNF_001 - Class in kr.co.rayful.ingw.vo
- NRS_INNF_001() - Constructor for class kr.co.rayful.ingw.vo.NRS_INNF_001
- NRS_INNF_001_RES - Class in kr.co.rayful.ingw.vo
- NRS_INNF_001_RES() - Constructor for class kr.co.rayful.ingw.vo.NRS_INNF_001_RES
- NRS_INNF_002 - Class in kr.co.rayful.ingw.vo
- NRS_INNF_002() - Constructor for class kr.co.rayful.ingw.vo.NRS_INNF_002
- NRS_INNF_002_RES - Class in kr.co.rayful.ingw.vo
- NRS_INNF_002_RES() - Constructor for class kr.co.rayful.ingw.vo.NRS_INNF_002_RES
- NRS_INNF_002_ROW - Class in kr.co.rayful.ingw.vo
- NRS_INNF_002_ROW() - Constructor for class kr.co.rayful.ingw.vo.NRS_INNF_002_ROW
- NRS_INNF_002_ROW2 - Class in kr.co.rayful.ingw.vo
- NRS_INNF_002_ROW2() - Constructor for class kr.co.rayful.ingw.vo.NRS_INNF_002_ROW2
- NRS_INNF_003 - Class in kr.co.rayful.ingw.vo
-
simple : 반제일 생성 엔티티.
- NRS_INNF_003() - Constructor for class kr.co.rayful.ingw.vo.NRS_INNF_003
- NRS_INNF_005 - Class in kr.co.rayful.ingw.vo
-
simple : 국세청 스마트빌 엔티티.
- NRS_INNF_005() - Constructor for class kr.co.rayful.ingw.vo.NRS_INNF_005
- NRS_INNF_006_01 - Class in kr.co.rayful.ingw.vo
-
simple : 관리자 정보(인사-개인) 엔티티.
- NRS_INNF_006_01() - Constructor for class kr.co.rayful.ingw.vo.NRS_INNF_006_01
- NRS_INNF_006_02 - Class in kr.co.rayful.ingw.vo
-
simple : 관리자 정보(인사-부서) 엔티티.
- NRS_INNF_006_02() - Constructor for class kr.co.rayful.ingw.vo.NRS_INNF_006_02
- NRS_INNF_007 - Class in kr.co.rayful.ingw.vo
-
simple : .
- NRS_INNF_007() - Constructor for class kr.co.rayful.ingw.vo.NRS_INNF_007
- NRS_INNF_007_RES - Class in kr.co.rayful.ingw.vo
-
simple : .
- NRS_INNF_007_RES() - Constructor for class kr.co.rayful.ingw.vo.NRS_INNF_007_RES
- NRS_INNF_008 - Class in kr.co.rayful.ingw.vo
-
simple : 자체설비 발전량(혼소) 엔티티.
- NRS_INNF_008() - Constructor for class kr.co.rayful.ingw.vo.NRS_INNF_008
- NRS_INNF_009 - Class in kr.co.rayful.ingw.vo
-
simple : 자체설비 연료 사용량 엔티티.
- NRS_INNF_009() - Constructor for class kr.co.rayful.ingw.vo.NRS_INNF_009
- NRS_INNF_010 - Class in kr.co.rayful.ingw.vo
-
simple : 전력거래 SMP 엔티티.
- NRS_INNF_010() - Constructor for class kr.co.rayful.ingw.vo.NRS_INNF_010
- NRS_INNF_011 - Class in kr.co.rayful.ingw.vo
-
simple : 은행정보 엔티티.
- NRS_INNF_011() - Constructor for class kr.co.rayful.ingw.vo.NRS_INNF_011
- NRS_INNF_012 - Class in kr.co.rayful.ingw.vo
-
simple : SMS 발송 정보 엔티티.
- NRS_INNF_012() - Constructor for class kr.co.rayful.ingw.vo.NRS_INNF_012
- NRS_INNF_013 - Class in kr.co.rayful.ingw.vo
-
simple : 전력거래 자체설비 발전량 엔티티.
- NRS_INNF_013() - Constructor for class kr.co.rayful.ingw.vo.NRS_INNF_013
All Classes|All Packages


PendingTransactionType
Transaction data encoded in hexadecimal string
{string}
Transaction fee in nano SEM
Sender's address
Transaction timestamp in milliseconds specified by the transaction creator. There can be a time drift up to 2 hours.
Recipient's address
Transaction value in nano SEM
Generated using TypeDoc
PendingTransactionType


A FUNNY THING HAPPENED ON THE WAY TO THE FORUM
Spring 1983
Director - Linda Nash & Wess Hughes
THE CAST
Pseudolus - Wess Hughes
Proteans - Larry Boyd, Robbie Everitt, Wayne Merritt, Mike Perry
Senex - Edward Boone
Domina - LaNeil Lucius
Hero - Paul Wade
Hysterium - Dwight Pitts
Marcus Lycus - Trey Carter
Philia - Marcia Wilson, Martie Allen
Erronius - Herb Knotts
Miles Gloriosus - Dwight Hampton
Courtesans
Linda Walton, Pearl Hinton, Kathy Clark,
Robin Duke, Billie Graham, Katie Samora


If we wanted to make a birthday cake, first we would start with html. Html is our base ( our cake ). We then use CSS to decorate the cake with icing and sprinkles.
Control flow is the order in which we go about our day and the loops are what we repeat. Breakfast Work Gym Netflix BedThe DOM ( Document object model ) is an object orientated representation of your HTML document. A webpage is a document not matter if it is opened in a browser or in a code editor. We can use JavaScript to modify your HTML code via the DOM.
There are two ways to access the properties of an object: the dot notation (.) and the bracket notation ( [ ] ) The Dot notation is what you use when you know the name of the property you’re trying to access ahead of time.
Let myObject = {
property1: “value1”
property2: “value2”
}
Let propertyValue = myObject.property1
We can access the data from arrays using square brackets. We Choose what entry in the array we would like by placing a number between the square brackets, the first element in an array has an index of 0.
Let array = [50,60,70];
array[0] would be equal to 50
Let data = array[1] would be equal to 60
Functions are a sequence of commands that take and input and give us an output. They are important because they are reusable and save us from repeating code.
Function addNumber( num1, num2 ) {
return num1 + num2
}
addNumber( 10, 15 )
Home


Figs For Italo
Cast
- DORA (present day) - Elinore Carrabba
- DIANE MORRETTI - Valerie Smaldone
- MARCO - Santino D' Amico
- GABRIELLA - Mara Baldissoni-Aceves
- YONG DORA - Francesca Procaccini
- ITALO - Claudio Brovedani Nuti
- WOMAN ON TRAIN - Teresa Russo
- TRAIN CONDUCTOR - Nino Spallacci
- YOUNG PEASANT WOMAN - Ariana Iacono
- MAN ON TRAIN - Frank Ingrasciotta
- GEORGE MILLER - John P. McGill
- THE FAMILY
- Sal Giordano
- Felicia Scarangello
- Carlo Iacono
- Linda Bloom-Coley
- Nicholas Palmieri
- Monica DeAntonio
- TRAIN PASSENGERS
- Shelley Gail Weiss Lightman
- Timothy Magidson
- Janet Stanwood
- Peggy DiPaolo
- Andres
- Maria Miroulis
- Nelson Miranda
- Tricia Gimon
- William Giaimo
- John Porras
- Kathi Troy
- Randi Senderowitz
- GERMAN SOLDIERS
- Jason Utnick
- Bob Brader
- Adam Brick
- TRAIN CREW
- John J. Stocker
- Nick Zisa
- Richard Butterworts
Credits
- Directors
- Bob Celli
- Screenwriters
- Bob Celli
- Producers
- Laura Delano, Bob Celli
Screenings
- "Winner Award of Excellence " 2015 Best Shorts Competition
Directors Statement
Many of us have grown up hearing stories of our families’ histories. These memories have the power to affect and alter lives. I have heard my family's stories of the time during and after World War II my entire life. It is one of these stories that has inspired me to make this film.
The experience I aspire to communicate with Figs For Italo is that of a journey. Not only a journey from point A to point B, but from past to present. The inspiration came to me after a conversation with a friend. We were discussing the possibility that we as humans have a collective connection; people connect on a sub-atomic level of shared energy. We are all recycled atoms of exploded stars when the universe expanded and formed itself. The more energy/atoms we share, the more we seek out and attempt to reconnect with our universal beginnings.
Sometimes those re-connections can be smooth and effortless; other times they can be turbulent.
runtime: 19 min
screening: July 7th


Class SingletonLifetimeManager
Singleton lifetime creates globally unique singleton. Any Unity container tree (parent and all the children) is guaranteed to have only one global singleton for the registered type.
Inherited Members
Namespace: Unity.Lifetime
Assembly: Unity.Abstractions.dll
Syntax
public class SingletonLifetimeManager : SynchronizedLifetimeManager, IDisposable, IInstanceLifetimeManager, IFactoryLifetimeManager, ITypeLifetimeManager
Remarks
Registering a type with singleton lifetime always places the registration at the root of the container tree and makes it globally available for all the children of that container. It does not matter if registration takes places at the root of child container the destination is always the root node.
Repeating the registration on any of the child nodes with singleton lifetime will always override the root registration.
When the SingletonLifetimeManager is disposed, the instance it holds is disposed with it.
Fields
| Improve this Doc View SourceValue
An instance of the singleton object this manager is associated with.
Declaration
protected object Value
Field Value
| Type | Description |
|---|---|
| Object | This field holds a strong reference to the singleton object. |
Methods
| Improve this Doc View SourceDispose(Boolean)
Standard Dispose pattern implementation.
Declaration
protected override void Dispose(bool disposing)
Parameters
| Type | Name | Description |
|---|---|---|
| Boolean | disposing | Always true, since we don't have a finalizer. |
Overrides
| Improve this Doc View SourceOnCreateLifetimeManager()
Implementation of CreateLifetimePolicy() policy.
Declaration
protected override LifetimeManager OnCreateLifetimeManager()
Returns
| Type | Description |
|---|---|
| LifetimeManager | A new instance of the same lifetime manager of appropriate type |
Overrides
| Improve this Doc View SourceRemoveValue(ILifetimeContainer)
Remove the given object from backing store.
Declaration
public override void RemoveValue(ILifetimeContainer container = null)
Parameters
| Type | Name | Description |
|---|---|---|
| ILifetimeContainer | container | The container this lifetime belongs to |
Overrides
| Improve this Doc View SourceSynchronizedGetValue(ILifetimeContainer)
Performs the actual retrieval of a value from the backing store associated with this Lifetime policy.
Declaration
protected override object SynchronizedGetValue(ILifetimeContainer container = null)
Parameters
| Type | Name | Description |
|---|---|---|
| ILifetimeContainer | container | Instance of the lifetime's container |
Returns
| Type | Description |
|---|---|
| Object | the object desired, or null if no such object is currently stored. |
Overrides
Remarks
This method is invoked by GetValue(ILifetimeContainer) after it has acquired its lock.
SynchronizedSetValue(Object, ILifetimeContainer)
Performs the actual storage of the given value into backing store for retrieval later.
Declaration
protected override void SynchronizedSetValue(object newValue, ILifetimeContainer container = null)
Parameters
| Type | Name | Description |
|---|---|---|
| Object | newValue | The object being stored. |
| ILifetimeContainer | container | Instance of the lifetime's container |
Overrides
Remarks
This method is invoked by SetValue(Object, ILifetimeContainer) before releasing its lock.
ToString()
This method provides human readable representation of the lifetime
Declaration
public override string ToString()
Returns
| Type | Description |
|---|---|
| String | Name of the lifetime |


Sunny skies, seasonal highs expected in week before Thanksgiving
by Marvin ClemonsThe week leading up to Thanksgiving will be close to seasonal norms for Las Vegas Valley residents.
Friday through Sunday will see clear skies, light winds and highs in the low 60s with overnight lows in the low to mid-40s, according to the National Weather Service forecast.
Monday will likely see the high for the week with 65 predicted before a steady dip in daytime highs through Thanksgiving when meteorologists forecast partly sunny skies with a chance of rain and a high of 54.
For potential weekend visitors to Mt. Charleston, skies should be clear this weekend with highs in the lower 40s. There is a chance for snow each day next week through Thanksgiving.
At Red Rock, the weekend forecast calls for sunny skies, highs in the low 50s with winds about 10 mph.


Get started on the right foot
150+ Employees In Facility
Able To Accomodate Employee Time
75+ Event Attendance
Let our safety footwear experts help you
CustomFit fitting events are an innovative approach to doing business in a digital age. Our safety footwear experts are ready to help your business and employees order great footwear right from the comfort of your own facility.
Speak to a repBenefits To You
- Employees gain safety footwear knowledge
- Increases program participation
- Promotes safety in the workplace
- Advanced Aetrex 3D foot scanner identifies potential foot/body ailments
- Reduces returns
- On-site access to safety footwear experts
Benefits To Us
- Better understanding of your work environment
- Chance to showcase new and best footwear
- Deeper engagement with employee needs and concerns
- Offers valuable feedback on how to improve service and selection
Think your facility qualifies for a Lehigh CustomFit Fitting Event? Contact one of our representatives today to find out how an event could save your company time and money.


2 references to First
Microsoft.PowerShell.Commands.Utility (1)
commands\utility\XmlCommands.cs (1)
747
ulong first = _cmdlet.PagingParameters.
First
;
System.Management.Automation (1)
engine\UserFeedbackParameters.cs (1)
58
/// (this can be more than the size of the page specified in the <see cref="
First
"/> cmdlet parameter).


- Source:
- lib/node-foursquare.js, line 28
Namespaces
Methods
-
<static> getAccessToken(params, callback)
-
Exchange a user authorization code for an access token.
- Source:
- lib/node-foursquare.js, line 189
- See:
-
- https://developer.foursquare.com/docs/oauth.html
Parameters:
Name Type Description params
Object A collection of parameters for the Access Token request. Properties
Name Type Argument Default Description code
String The code provided by Foursquare as the result of the user redirect. redirect_uri
String The URL to redirect to after the code is exchanged for a token. client_id
String The Client ID provided by Foursquare. client_secret
String The Client Secret provided by Foursquare. grant_type
String <optional>
"authorization_code" The type of authorization to request. callback
Function The function to call with results, function({Error} error, {Object} results). -
<static> getAuthClientRedirectUrl(clientId, redirectUrl)
-
Build and return an appropriate Authorization URL where the user can grant permission to the application.
- Source:
- lib/node-foursquare.js, line 223
Parameters:
Name Type Description clientId
String The Client ID provided by Foursquare redirectUrl
String The URL to redirect to after authorization is granted.


Fragments Review - Amy Sanderson
Over on her wonderfully titled blog, Not All Those Who Wander, Amy Sanderson (author of Sanguine) posted what—to my knowledge—is the first public review of Fragments.
Check it out. It’s always exciting to see feedback from readers. I hope that Amy is just the first of many. Not only is it a great feeling to see what people think of Askon’s adventure, every time someone rates or reviews the book, it helps the audience grow. So, thanks to Amy and thanks to all the future reviewers that are out there enjoying (I sincerely hope) the story right now.


{include file="../application/index/view/public/_header2.html"}
{$Think.lang.you_profile}
{$Think.lang.first_name}:
{$Think.lang.last_name}:
{$Think.lang.home_address}:
{$Think.lang.wechat}:
{$Think.lang.gender}:
{$Think.lang.male}
{$Think.lang.female}
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.


PSX trounces rest of the world in past three months: report
by https://www.facebook.com/dunyanews(Web Desk) – Pakistan’s KSE-100 Index has advanced to the highest level in seven months, after falling to the lowest in almost five years in August, amid attempts by the government to stabilize the economy with a $6 billion loan from the International Monetary Fund after a deficit blowout.
According to a report published in the Bloomberg, the rally that’s helped Pakistan stocks trounce the rest of the world in the past three months isn’t done yet. At the same time, bond yields have begun to fall after peaking around 14% mid-year, making debt investments less attractive.
Large investors, including mutual funds and insurers, are expected to jump in as double-digit returns from fixed income have begun to ebb away.
The report further said, “Banks are rethinking their strategy. They have to look at riskier assets now. So, the stock market is a tempting bet.”
With stocks trading at overbought levels, it’s probably inevitable there’s a pause for breath, the report said. The rally will resume as more investors come in. The KSE-100 fell on Wednesday after five straight days of gains.
Foreign investors have bought $64 million of the nation’s stocks this year, set for the first annual inflow since 2014. Their purchases will gather pace February after the nation’s next review by the Financial Action Task Force, the report added.


|
BL3 SDK
0.0.1
Borderlands 3 Class Documentation
|
#include <BL3_Engine_classes.hpp>
Public Member Functions | |
| void | StopSimulating (const struct FHitResult &HitResult) |
| void | SetVelocityInLocalSpace (const struct FVector &NewVelocity) |
| void | OnProjectileStopDelegate__DelegateSignature (const struct FHitResult &ImpactResult) |
| void | OnProjectileBounceDelegate__DelegateSignature (const struct FHitResult &ImpactResult, const struct FVector &ImpactVelocity) |
| struct FVector | LimitVelocity (const struct FVector &NewVelocity) |
| Public Member Functions inherited from UMovementComponent | |
| void | StopMovementImmediately () |
| void | SnapUpdatedComponentToPlane () |
| void | SetUpdatedComponent (class USceneComponent *NewUpdatedComponent) |
| void | SetPlaneConstraintOrigin (const struct FVector &PlaneOrigin) |
| void | SetPlaneConstraintNormal (const struct FVector &PlaneNormal) |
| void | SetPlaneConstraintFromVectors (const struct FVector &Forward, const struct FVector &Up) |
| void | SetPlaneConstraintEnabled (bool bEnabled) |
| void | SetPlaneConstraintAxisSetting (EPlaneConstraintAxisSetting NewAxisSetting) |
| void | PhysicsVolumeChanged (class APhysicsVolume *NewVolume) |
| bool | K2_MoveUpdatedComponent (const struct FVector &Delta, const struct FRotator &NewRotation, bool bSweep, bool bTeleport, struct FHitResult *OutHit) |
| float | K2_GetModifiedMaxSpeed () |
| float | K2_GetMaxSpeedModifier () |
| bool | IsExceedingMaxSpeed (float MaxSpeed) |
| struct FVector | GetPlaneConstraintOrigin () |
| struct FVector | GetPlaneConstraintNormal () |
| EPlaneConstraintAxisSetting | GetPlaneConstraintAxisSetting () |
| class APhysicsVolume * | GetPhysicsVolume () |
| float | GetMaxSpeed () |
| float | GetGravityZ () |
| struct FVector | ConstrainNormalToPlane (const struct FVector &Normal) |
| struct FVector | ConstrainLocationToPlane (const struct FVector &Location) |
| struct FVector | ConstrainDirectionToPlane (const struct FVector &Direction) |
| Public Member Functions inherited from UActorComponent | |
| void | ToggleActive () |
| void | SetTickGroup (TEnumAsByte< ETickingGroup > NewTickGroup) |
| void | SetTickableWhenPaused (bool bTickableWhenPaused) |
| void | SetOwningSceneCapture (class USceneCaptureComponent *InOwningSceneCapture) |
| void | SetIsReplicated (bool ShouldReplicate) |
| void | SetComponentTickInterval (float TickInterval) |
| void | SetComponentTickEnabled (bool bEnabled) |
| void | SetAutoActivate (bool bNewAutoActivate) |
| void | SetActive (bool bNewActive, bool bReset) |
| void | RemoveTickPrerequisiteComponent (class UActorComponent *PrerequisiteComponent) |
| void | RemoveTickPrerequisiteActor (class AActor *PrerequisiteActor) |
| void | ReceiveTick (float DeltaSeconds) |
| void | ReceiveEndPlay (TEnumAsByte< EEndPlayReason > EndPlayReason) |
| void | ReceiveBeginPlay () |
| void | OnRep_IsActive () |
| void | MarkNetDirty () |
| void | K2_DestroyComponent (class UObject *Object) |
| bool | IsComponentTickEnabled () |
| bool | IsBeingDestroyed () |
| bool | IsActive () |
| class USceneCaptureComponent * | GetOwningSceneCapture () |
| class AActor * | GetOwner () |
| float | GetComponentTickInterval () |
| void | Deactivate () |
| bool | ComponentHasTag (const struct FName &Tag) |
| void | AddTickPrerequisiteComponent (class UActorComponent *PrerequisiteComponent) |
| void | AddTickPrerequisiteActor (class AActor *PrerequisiteActor) |
| void | Activate (bool bReset) |
| Public Member Functions inherited from UObject | |
| std::string | GetName () const |
| std::string | GetFullName () const |
| bool | IsA (UClass *cmp) const |
| void | ProcessEvent (class UFunction *function, void *parms) |
| void | ExecuteUbergraph (int EntryPoint) |
Static Public Member Functions | |
| static UClass * | StaticClass () |
| Static Public Member Functions inherited from UMovementComponent | |
| static UClass * | StaticClass () |
| Static Public Member Functions inherited from UActorComponent | |
| static UClass * | StaticClass () |
| Static Public Member Functions inherited from UObject | |
| static FChunkedFixedUObjectArray & | GetGlobalObjects () |
| template<typename T > | |
| static T * | FindObject (const std::string &name) |
| static UClass * | FindClass (const std::string &name) |
| template<typename T > | |
| static T * | GetObjectCasted (std::size_t index) |
| static UClass * | StaticClass () |
Additional Inherited Members | |
| Static Public Attributes inherited from UObject | |
| static FUObjectArray * | GObjects |
| void OnProjectileBounceDelegate__DelegateSignature | ( | const struct FHitResult & | ImpactResult, |
| const struct FVector & | ImpactVelocity | ||
| ) |
| void OnProjectileStopDelegate__DelegateSignature | ( | const struct FHitResult & | ImpactResult | ) |
| void SetVelocityInLocalSpace | ( | const struct FVector & | NewVelocity | ) |
|
inlinestatic |
| void StopSimulating | ( | const struct FHitResult & | HitResult | ) |
| struct FRotator BaseRotationOffset |
| unsigned char bBounceAngleAffectsFriction |
| unsigned char bForceSubStepping |
| unsigned char bInitialVelocityInLocalSpace |
| unsigned char bIsHomingProjectile |
| unsigned char bIsSliding |
| int BounceAdditionalIterations |
| float BounceVelocityStopSimulatingThreshold |
| float Bounciness |
| unsigned char bRotationFollowsVelocity |
| unsigned char bShouldBounce |
| float Buoyancy |
| float Friction |
| float HomingAccelerationMagnitude |
| TWeakObjectPtr<class USceneComponent> HomingTargetComponent |
| float InitialSpeed |
| int MaxSimulationIterations |
| float MaxSimulationTimeStep |
| float MaxSpeed |
| struct FScriptMulticastDelegate OnProjectileBounce |
| struct FScriptMulticastDelegate OnProjectileStop |
| struct FVector PreviousHitNormal |
| float PreviousHitTime |
| float ProjectileGravityScale |
| unsigned char UnknownData00[0x3] |
| unsigned char UnknownData01[0x24] |


The Tale of Tommy Fox
by Arthur Scott Bailey
Chapter 19: “Tommy Fox Learns a New Trick”
Additional Information
- Year Published: 1917
- Language: English
- Country of Origin: United States of America
- Source: Bailey, A. S. (1917). The Tale of Tommy Fox. New York: Grosset and Dunlap.
-
Readability:
- Flesch–Kincaid Level: 4.0
- Word Count: 614
- Genre: Fantasy
- Keywords: 20th century literature, american literature, children's stories, sleepy-time tales
- ✎ Cite This
Downloads
Now, there was a road that ran through the valley, along the bank of Swift River. And when Mrs. Fox reached it, with Tommy close behind her, she turned again—this time to the left—and ran along in the beaten track which the horses and sleighs had made.
Tommy Fox thought it very strange that his mother should lead him to the road, where they were sure to find people driving. Tommy followed her. But he was very unhappy. They swung into the road just ahead of a farmer, who was driving along in a sleigh. The sleigh-bells tinkled merrily as the horse trotted smartly down the road. But the jingling of the bells did not sound at all pleasant to Tommy Fox. It only frightened him all the more.
The farmer in the sleigh did not see Tommy and his mother, for the snow rose high on both sides, and the road wound in and out. Little did he know that Mrs. Fox and Tommy were scampering along in front of him. Of course, he couldn’t catch them, anyhow. Tommy knew that much. But if they ran very far down the road they would be sure to meet some other man.
To Tommy it seemed bad enough to have that dog chasing them, without going where they were sure to find other enemies. Tommy could hear the dog baying. And he knew dogs well enough to know that that dog felt very sure he was going to catch them. But pretty soon Tommy heard the dog talking in a very different fashion. He gave a number of short barks, which meant that he was in trouble.
Mrs. Fox looked over her shoulder and smiled at Tommy. She knew that they were safe. She knew that the dog had not reached the road until the farmer had driven right over their footsteps and spoiled their scent. After the horse had passed over their trail the dog could smell only the horse’s footprints, instead of theirs. And Mrs. Fox could tell what was happening back there in the road. She knew just exactly as well as if she had been there herself—she knew that the dog had stopped short, and was running all around, with his nose to the ground, trying to find where she and Tommy had gone. But he never found out.
You see, he wasn’t half as clever as Mrs. Fox. It never once occurred to him that Tommy and his mother had turned into the road just ahead of that farmer in his sleigh.
By that time Mrs. Fox and Tommy were safe at home. Yes—they were even having a good laugh over the way they had fooled the dog. And Tommy had quite forgotten how frightened he had been. In fact, he began to feel very well pleased with himself. For he never once remembered that it was his mother, and not himself, who had thought of that trick.  But Tommy Fox was so conceited that if his grandmother had been there with them he would have thought he knew ten times as much as she did.


--- layout: article ---
Got a question? We'd love to hear from you. Send us a message and we'll respond as soon as possible.


E
- Type of Abstract_Cell represented by this CellViewpublic abstract class AbstractRegularPolygon_CellView<E extends Abstract_Cell> extends Abstract_CellView<E>
Created by th174 on 2/8/2017.
Abstract_CellView
| Modifier and Type | Field and Description |
|---|---|
static double |
FULL_CIRCLE |
| Constructor and Description |
|---|
AbstractRegularPolygon_CellView(E cell,
java.lang.String outlineColor)
Constructs regular polygonal cell view of a regular polygon (e.g.
|
| Modifier and Type | Method and Description |
|---|---|
protected abstract double |
calculateX(double visibleColumns,
double visibleRows,
double windowWidth,
double windowHeight) |
protected abstract double |
calculateY(double visibleColumns,
double visibleRows,
double windowWidth,
double windowHeight) |
protected abstract int |
getNumSides() |
protected abstract double |
getRadius(double visibleColumns,
double visibleRows,
double windowWidth,
double windowHeight) |
protected abstract double |
getRotationAngle() |
javafx.scene.shape.Polygon |
getView() |
void |
updateView(double visibleColumns,
double visibleRows,
double windowWidth,
double windowHeight) |
getCell, setHueShift, setLightnessShift, setSaturationShift, setView
public static final double FULL_CIRCLE
public AbstractRegularPolygon_CellView(E cell, java.lang.String outlineColor)
cell
- Abstract_Cell that this CellView representsoutlineColor
- String representing the color of the grid outline of this CellView. The format of the string representation is the same as in web(String)public void updateView(double visibleColumns, double visibleRows, double windowWidth, double windowHeight)
updateView
in class Abstract_CellView<E extends Abstract_Cell>
visibleColumns
- Number of visible columns in the simulation windowvisibleRows
- Number of visible rows in the simulation windowwindowWidth
- Width of window in pixelswindowHeight
- Height of window in pixelsAbstract_CellView.updateView(double, double, double, double)
protected abstract int getNumSides()
protected abstract double getRotationAngle()
protected abstract double getRadius(double visibleColumns, double visibleRows, double windowWidth, double windowHeight)
visibleColumns
- Number of visible columns in the simulation windowvisibleRows
- Number of visible rows in the simulation windowwindowWidth
- Width of window in pixelswindowHeight
- Height of window in pixelsprotected abstract double calculateX(double visibleColumns, double visibleRows, double windowWidth, double windowHeight)
visibleColumns
- Number of visible columns in the simulation windowvisibleRows
- Number of visible rows in the simulation windowwindowWidth
- Width of window in pixelswindowHeight
- Height of window in pixelsprotected abstract double calculateY(double visibleColumns, double visibleRows, double windowWidth, double windowHeight)
visibleColumns
- Number of visible columns in the simulation windowvisibleRows
- Number of visible rows in the simulation windowwindowWidth
- Width of window in pixelswindowHeight
- Height of window in pixelspublic javafx.scene.shape.Polygon getView()
getView
in class Abstract_CellView<E extends Abstract_Cell>
Abstract_CellView.getView()


--- layout: post title: Delegates and Optional Parameters date: 2009-08-25 12:24:25.000000000 +02:00 categories: [] tags: - C# 4.0 - Delegates - Optional Parameters status: publish type: post published: true meta: _edit_last: '1' author: login: admin email<EMAIL_ADDRESS>display_name: Philippe first_name: Philippe last_name: Vlérick excerpt: !ruby/object:Hpricot::Doc options: {} ---
C# 4.0 adds a bunch of new features, amongst which there is the Optional Parameters. If you don’t know about them and their drawbacks, please read this.
So, using this new syntax, you can specify so of the parameters to be optional, and have a default value in case they are not specified. Did you know that this applies to delegates too?
Here’s a simple delegate type declaration:
delegate void PrintName(String name = "Philippe");
Given this delegate type, you could think that any method receiving an optional String parameter and returning void would fit. Actually, it’s not the case. Any method receiving a String parameter and returning void will fit. If the parameter is not given when invoking the delegate, the optional value of the parameter will be used.
Here is a working example:
static void PrintToScreen(String name) { Console.WriteLine("Hello in console from {0}", name); } static void Main(string[] args) { PrintName p = OptionalsParametersOnDelegates.PrintToScreen; p(); }
This code will call the methods PrintToScreen with “Philippe” as argument for the name parameter. The delegate instance p can also be called with any String argument, which will be passed to the methods in the delegate invocation list.
Now, what happens if the method PrintToScreen also has an optional argument?
static void PrintToScreen(String name = "Bill") { Console.WriteLine("Hello in console from {0}", name); }
Making the name parameter optional and giving it a default value will not change the output of the previous code. It’s actually quite easy to explain: when the delegate instance is called with no parameter, the methods in the invocation list are called with the default value of parameter defined in the delegate type, in this case “Philippe”. If it is called with an argument, then the argument is passed along to the methods in the invocation list.


| Supermacss €5.50 |
Cheese Burger €2.20 |
Chicken Burger €4.20 |
Mighty Mac €4.20 |
Grilled Chicken €5.50 |
| Veggie Burger€3.20 |
Bucket €7.80 |
Chips €2.30 |
Cod Chips €5.45 |
Garlic Cheese €3.45 |
| Chicken Wrap €4.45 |
Kids Burger €1.80 |
Ice Cream€1.75 |
Milk Shake €2.50 |
Minerals €1.70 |


|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: INNER | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
java.lang.Object | +--org.apache.commons.lang.CharRange
A contiguous range of characters, optionally negated.
Instances are immutable.
| Constructor Summary | |
CharRange(char ch)
Constructs a CharRange over a single character. |
|
CharRange(char ch,
boolean negated)
Constructs a CharRange over a single character,
optionally negating the range. |
|
CharRange(char start,
char end)
Constructs a CharRange over a set of characters. |
|
CharRange(char start,
char end,
boolean negated)
Constructs a CharRange over a set of characters,
optionally negating the range. |
| Method Summary | |
boolean |
contains(char ch)
Is the character specified contained in this range. |
boolean |
contains(CharRange range)
Are all the characters of the passed in range contained in this range. |
boolean |
equals(Object obj)
Compares two CharRange objects, returning true if they represent exactly the same range of characters defined in the same way. |
char |
getEnd()
Gets the end character for this character range. |
char |
getStart()
Gets the start character for this character range. |
int |
hashCode()
Gets a hashCode compatible with the equals method. |
boolean |
isNegated()
Is this CharRange negated. |
String |
toString()
Gets a string representation of the character range. |
| Methods inherited from class java.lang.Object |
clone,
finalize,
getClass,
notify,
notifyAll,
wait,
wait,
wait |
| Constructor Detail |
public CharRange(char ch)
Constructs a CharRange
over a single character.
ch
- only character in this rangepublic CharRange(char ch, boolean negated)
Constructs a CharRange
over a single character,
optionally negating the range.
A negated range includes everything except the specified char.
ch
- only character in this rangenegated
- true to express everything except the rangepublic CharRange(char start, char end)
Constructs a CharRange
over a set of characters.
start
- first character, inclusive, in this rangeend
- last character, inclusive, in this rangepublic CharRange(char start, char end, boolean negated)
Constructs a CharRange
over a set of characters,
optionally negating the range.
A negated range includes everything except that defined by the start and end characters.
If start and end are in the wrong order, they are reversed.
Thus a-e
is the same as e-a
.
start
- first character, inclusive, in this rangeend
- last character, inclusive, in this rangenegated
- true to express everything except the range| Method Detail |
public char getStart()
Gets the start character for this character range.
public char getEnd()
Gets the end character for this character range.
public boolean isNegated()
Is this CharRange
negated.
A negated range includes everything except that defined by the start and end characters.
true
is negatedpublic boolean contains(char ch)
Is the character specified contained in this range.
ch
- the character to checktrue
if this range contains the input characterpublic boolean contains(CharRange range)
Are all the characters of the passed in range contained in this range.
range
- the range to check againsttrue
if this range entirely contains the input rangenull
inputpublic boolean equals(Object obj)
Compares two CharRange objects, returning true if they represent exactly the same range of characters defined in the same way.
obj
- the object to compare topublic int hashCode()
Gets a hashCode compatible with the equals method.
public String toString()
Gets a string representation of the character range.
|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: INNER | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |


1.5.6 - 30-Jul-2011
- Fixed issue for non-gnu platforms where it would use the wrong function
prototype because the Ruby core team took it upon themselves to explicitly
defined _GNU_SOURCE in config.h in 1.8.7 and later for reasons that baffle
me.
- Some tests on Windows are now skipped unless run with elevated security.
1.5.5 - 5-Jul-2011
- Modified lastlog handling, and ignore getpwent_r and getgrent_r, on AIX.
Thanks go to Rick Ohnemus for the spot and patches.
- Explicitly set spec.cpu on Windows to ‘universal’ in the gem
creation task.
- Fixed a bug in the User.get_login and User.get_group methods where the
query being generated was incorrect if no options were passed. Thanks go to
Matthew Brown for the spot.
1.5.4 - 7-Oct-2010
- Prefer the getlastlogx() function over lastlog() where supported.
1.5.3 - 6-Oct-2010
- Refactored the Rakefile. The old installation tasks have been replaced with
gem build and install tasks. In addition, the platform handling has been
updated for MS Windows.
- Portions of the gemspec have been moved into the Rakefile gem tasks.
- Deploying the mingw gem by default for MS Windows now.
1.5.2 - 2-Aug-2009
- Now compatible with Ruby 1.9.x.
- Added test-unit as a development dependency.
1.5.1 - 23-Jul-2009
- Added the User#dir attribute. This attribute contains a user‘s home
directory if set, or nil if it isn‘t.
- User objects returned by the Admin.users method now include the uid.
Previously only the Admin.get_user method set it.
- Added win32-security as a dependency.
- Changed license to Artistic 2.0.
1.5.0 - 29-Mar-2009
- INTERFACE CHANGE (WINDOWS ONLY): The interface for MS Windows has undergone
a radical change. Most methods now accept a hash of options that are passed
directly to the underlying WMI class. Please see the documentation for
details.
- Now works on various BSD flavors.
- Added the User#groups method. This returns an array of groups that the user
belongs to. Suggestion inspired by Gonzalo Garramuno.
- Added the Group#members method. The returns an array of users that the
group contains.
- Changed User#class to User#access_class for UNIX flavors to avoid conflicts
with the Ruby core Object method.
- Added more tests and renamed the test files.
- Removed an unnecessary function call where a platform might try to get
lastlog information even if the lastlog.h or utmp.h headers couldn‘t
be found.
1.4.4 - 19-Nov-2008
- Added the User#uid method for MS Windows (which is just the user‘s
relative identifier).
- Now requires test-unit 2.x.
- Some updates to the test suite to take advantage of test-unit 2.x features.
- Some minor gemspec tweaks.
1.4.3 - 2-Mar-2008
- The block form of Admin.users now properly ensures that endpwent() is
called. Likewise, the block form of Admin.groups now properly ensures that
endgrent() is called. This would only have been an issue if you broke out
of the block before it terminated.
- The AdminError class is now Admin::Error.
- Some internal directory layout changes.
1.4.2 - 26-Jun-2007
- Fixed a bug in the Admin.get_login method where it would return junk if the
underlying getlogin() function failed (Unix). Thanks go to Gonzalo
Garramuno for the spot. This bug also resulted in some refactoring of the
underlying C code.
- Removed the install.rb file. The logic in that file has been moved directly
into the Rakefile.
1.4.1 - 21-Mar-2007
- Bug fix for OS X. Thanks go to an anonymous user for the spot.
- Added a Rakefile. Building, testing and installing should now use the Rake
tasks (for non-gem installs).
- Much more inline documentation, especially for User and Group attributes.
1.4.0 - 20-Jan-2007
- Added the following methods: add_local_user, config_local_user,
delete_local_user, add_global_group, config_global_group, and
delete_global_group. MS Windows only at the moment.
- Added corresponding tests.
- Added much more inline documentation.
- Major refactoring of the get_lastlog_info helper function in admin.h. This
fixed a major bug in some flavors of Linux where the Admin.users method
could go into an infinite loop. It also fixed some minor bugs where console
and host values were sometimes filled with junk characters.
- Added the User#change attribute, and a check for the pw_change struct
member in the extconf.rb file.
- The User#expire attribute is now handled as a Time object instead of an
integer.
- Renamed tc_win32.rb to tc_windows.rb
1.3.1 - 29-Jun-2005
- Fixed a bug where the inability to read the lastlog file caused an error.
From now on that error is ignored, and the lastlog attributes of the User
object are set to nil.
- Added a beta version of Admin.delete_user (Windows only).
1.3.0 - 3-Jun-2005
- Bug fixes for Linux.
- Removed the version.h file - no longer needed since the Win32 version is
pure Ruby.
1.2.0 - 30-Apr-2005
- Replaced the Win32 version with a pure Ruby version that uses Win32API and
win32ole + WMI.
- The LocalGroup class no longer exists in the Win32 version. Instead, it is
now an attribute of a Group object. The issue was forced by WMI.
- The default for users and groups on Win32 systems is now local rather than
global. See the documentation for why you probably don‘t want to
iterate over global accounts.
- Corresponding doc changes and test suite changes.
1.1.0 - 1-Apr-2005
- Fixed bug where a segfault could occur when trying to retrieve a user or
group by an ID that didn‘t exist (Unix).
- Added tests for intentional failures.
- Added lastlog information tothe User class (Unix).
- Modified the way User objects are created internally (Unix).
- Fixed a bug in the User#shell attribute (Unix).
1.0.0 - 25-Mar-2005


James
Levine
SimplyHired
Microformat Brainstormer
James
Levine
SimplyHired
Microformat Brainstormer
example from
include-pattern
wiki topic last modified 08:58, 2 Mar 2006.