As shown in Figure-1, Generic Resource Adapter wraps the JMS client library of the JMS provider. The Resource Adapter can be configured to use either reflection or JNDI lookup as the way to obtain JMS Administered Objects for its internal operation. These administered objects are used as the basic gateway to contact the JMS provider for both inbound and outbound communication. The Resource Adapter can be configured to indicate whether the JMS provider supports XA or not. Configuration details are described below .
When a QueueConnectionFactory is created using the Generic
Resource Adapter, it will use QueueConnectionFactory
or XAQueueConnectionFactory
implementation of the JMS provider, internally, to execute JMS and
Transactional JMS operations. The resource adapter will create such an
internal administered object either by reflection or by looking up JNDI
provider of the JMS provider, depending upon its configuration settings.
For achieving inbound communication to message
driven beans, Generic Resource Adapter depends on the JMS optional
functionality called ConnectionConsumer
/ServerSessionPool. It is expected that most of the JMS
providers will implement ConnectionConsumer
functionality as specified in chapter 8 of the JMS 1.1 specification,
even though it is optional. Similar to outbound communication, resource
adapter uses JMS administered objects to communicate with the JMS
provider. For example, to receive messages from the JMS provider,
resource adapter will create (or lookup) a ConnectionFactory implementation of
the JMS provider and create a ConnectionConsumer.
A J2EE 1.4 application server's administration tools
can be used to deploy and configure Generic Resource Adapter for JMS.
This section explains how to configure Generic Resource Adapter for JMS
with Sun Java System Application Server. Overall the Resource
Adapter can be configured to indicate whether JMS provider supports XA
or not. It is also possible to indicate what mode of integration is
possible with JMS provider. Two modes of integration is supported by the
Resource Adapter. First one uses JNDI as the means of integration. In
this case, administered objects are setup in JMS provider's JNDI tree
and will be looked up for use by the Generic Resource Adapter resources.
If that mode is not suitable for integration, it is also possible to
use java reflection of JMS administered object javabean classes as the
mode of integration.
Users can use either the Sun Java System Application server's admin GUI or CLI to configure the resource adapter. This is not different from configuring any other resource adapter. More information about how to use a resource adapter with application server is available in the Adminsitratiion Guide and Developers Guide of the Application Server 8.1
Prior to deploying the resource adapter JMS client libraries should be made available to the application server. For some JMS providers, client libraries may also include native libraries. In such cases, these native libraries should also be made available to the application server JVM(s).
Following steps could be used to deploy the resource adapter and configure the resources to work with SJSMQ. For some other JMS provider, though steps would remain the same, the information will change.
Deploying the resource
adapter:
1)asadmin
create-resource-adapter-config --user admin --password adminadmin
--property
SupportsXA=true:ProviderIntegrationMode=javabean:ConnectionFactoryClassName=com.sun.messaging.ConnectionFactory:\
CommonSetterMethodName=setProperty:UserName=guest:Password=guest:\
QueueConnectionFactoryClassName=com.sun.messaging.QueueConnectionFactory:\
TopicConnectionFactoryClassName=com.sun.messaging.TopicConnectionFactory:\
QueueClassName=com.sun.messaging.Queue:TopicClassName=com.sun.messaging.Topic:\
LogLevel=info:UserName=guest:Password=guest:XAQueueConnectionFactoryClassName=com.sun.messaging.XAQueueConnectionFactory:\
XATopicConnectionFactoryClassName=com.sun.messaging.XATopicConnectionFactory:\
XAConnectionFactoryClassName=com.sun.messaging.XAConnectionFactory
genericra
2)asadmin deploy --user admin --password adminadmin /tmp/genericra.rar
1)asadmin create-connector-connection-pool --raname genericra --connectiondefinition javax.jms.QueueConnectionFactory qcpool
2)asadmin create-connector-resource --poolname qcpool jms/QCFactory
1)asadmin create-admin-object --raname genericra --restype javax.jms.Queue --property DestinationProperties=Name\\=clientQueue jms/clientQueue
Following is an example of a sun-ejb-jar.xml configured to use Generic Resource Adapter for JMS instead of default Sun Java System Message Queue.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE
sun-ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Application
Server 8.1 EJB 2.1//EN'
'http://www.sun.com/software/sunone/appserver/dtds/sun-ejb-jar_2_1-1.dtd'>
<!-- Copyright
2002 Sun Microsystems, Inc. All rights reserved. -->
<sun-ejb-jar>
<enterprise-beans>
<unique-id>1</unique-id>
<ejb>
<ejb-name>SimpleMessageEJB</ejb-name>
<jndi-name>jms/SampleQueue</jndi-name>
<resource-ref>
<res-ref-name>jms/QCFactory</res-ref-name>
<!--
jndi-name below should be the name of connector-resource created in step 1 of configuration section above
-->
<jndi-name>jms/QCFactory</jndi-name>
<default-resource-principal>
<name>guest</name>
<password>guest</password>
</default-resource-principal>
</resource-ref>
<resource-env-ref>
<resource-env-ref-name>jms/clientQueue</resource-env-ref-name>
<!--
jndi-name below should be the name of admin-object-resource created in step 2 of section above
-->
<jndi-name>jms/clientQueue</jndi-name>
</resource-env-ref>
<mdb-resource-adapter>
<!--  Modify
<SJSAS_HOME>/domains/domain1/config/server.policy to add
java.util.logging.LoggingPermission "control"
2. Modify
<SJS_HOME>/lib/appclient/client.policy to add
permission javax.security.auth.PrivateCredentialPermission
"javax.resource.spi.security.PasswordCredential * \"*\"","read";
To run a client JMS application, either as a
standalone java application or bundled as an appclient, make sure that
the genericra.jar
is part of the classpath. genericra.jar
is available as part of generic ra distribution. It is also bundled in .rar archive.
All configuration requirements for JMS client
library (including setting of classpath) should also be fullfilled prior
to running the client applications. Since these configurations vary
across JMS providers, it is not included in this document.
These properties
will be used in create-resource-adapter-config command.
|
Property Name |
Valid Values |
Default Value |
Description |
|---|---|---|---|
|
ProviderIntegrationMode |
javabean/jndi |
javabean |
Decides the mode of integration to be used between resource adapter and jms client. |
|
ConnectionFactoryClassName |
Name of the class available in appserver classpath (eg: com.sun.messaging.ConnectionFactory) |
NA |
Class Name of javax.jms.ConnectionFactory implementation of the jms client. Used if ProviderIntegrationMode is specified as “javabean” |
|
QueueConnectionFactoryClassName |
Name of the class available in appserver classpath (eg: com.sun.messaging.QueueConnectionFactory) |
NA |
Class Name of javax.jms.QueueConnectionFactory implementation of the jms client. Used if ProviderIntegrationMode is specified as “javabean” |
|
TopicConnectionFactoryClassName |
Name of the class available in appserver classpath (eg: com.sun.messaging.TopicConnectionFactory) |
NA |
Class Name of javax.jms.TopicConnectionFactory implementation of the jms client. Used if ProviderIntegrationMode is specified as “javabean” |
|
XAConnectionFactoryClassName |
Name of the class available in appserver classpath (eg: com.sun.messaging.XAConnectionFactory) |
NA |
Class Name of javax.jms.ConnectionFactory implementation of the jms client. Used if ProviderIntegrationMode is specified as “javabean” |
|
XAQueueConnectionFactoryClassName |
Name of the class available in appserver classpath (eg: com.sun.messaging.XAQueueConnectionFactory) |
NA |
Class Name of javax.jms.XAQueueConnectionFactory implementation of the jms client. Used if ProviderIntegrationMode is specified as “javabean” |
|
XATopicConnectionFactoryClassName |
Name of the class available in appserver classpath (eg: com.sun.messaging.XATopicConnectionFactory) |
NA |
Class Name of javax.jms.XATopicConnectionFactory implementation of the jms client. Used if ProviderIntegrationMode is specified as “javabean” |
|
TopicClassName |
Name of the class available in appserver classpath (eg: com.sun.messaging.Topic) |
NA |
Class Name of javax.jms.Topic implementation of the jms client. Used if ProviderIntegrationMode is specified as “javabean” |
|
QueueClassName |
Name of the class available in appserver classpath (eg: com.sun.messaging.Queue) |
NA |
Class Name of javax.jms.Queue implementation of the jms client. Used if ProviderIntegrationMode is specified as “javabean” |
|
SupportsXA |
True/false |
FALSE |
Specifies whether the jms client supports XA or not. |
|
ConnectionFactoryProperties |
Name value pairs separated by comma. |
NA |
This specifies the javabean propery names and values of the ConnectionFactory of jms client. Required only if ProviderIntegrationMode is “javabean” |
|
JndiProperties |
Name value pairs separated by comma. |
NA |
This specifies JNDI provider properties to be used for connecting to JMS provider's JNDI. Used only if ProviderIntegrationMode is “jndi” |
|
CommonSetterMethodName |
Method name. |
NA |
This specifies the common setter method name some JMS vendors use to set the properties on their administered objects. Used only if ProviderIntegrationMode is “javabean”. In case of SJSMQ, this value is “setProperty” |
|
UserName |
Name of JMS user |
NA |
UserName to connect to JMS Provider. |
|
Password |
Password for JMS user. |
NA |
Password to connect to JMS provider. |
ManagedConnectionFactory Properties
ManagedConnectionFactory properties are specified when a
connector-connection-pool is created. All the properties specified in resource adapter section can be
overridden in a ManagedConnectionFactory. Additional properties
available only in ManagedConnectionFactory are given below.
|
Property Name |
Valid Value. |
Default Value. |
Description |
|---|---|---|---|
|
ClientId |
A valid client ID |
NA |
ClientID as specified by jms 1.1 specification. |
|
ConnectionFactoryJndiName |
JNDI Name |
NA |
JNDI name of the connection factory bound in JNDI tree of JMS provider. Administrator should provide all connection factory properties (except clientID) in the JMS provider itself. This property name will be used only if ProviderIntegratinMode is “jndi”. |
|
ConnectionValidationEnabled |
true/false |
FALSE |
If set to true, resource adapter will use an exception listener to catch any connection exception and will send a CONNECTION_ERROR_OCCURED event to application server. |
AdminObject Properties.
Properties in this section are specified when a connector-admin-object is created. All the properties specified in resource adapter section can be overridden in an AdminObject. Additional properties available only in AdminObject are given below.
|
Property Name |
Valid Values. |
Default Value. |
Description |
|---|---|---|---|
|
DestinationJndiName |
Jndi Name |
NA |
JNDI name of the destination bound in JNDI tree of JMS provider. Administrator should provide all properties in the JMS provider itself. This property name will be used only if ProviderIntegrationMode is “jndi”. |
|
DestinationProperties |
Name value pairs separated by comma |
|
This specifies the javabean propery names and values of the Destination of jms client. Required only if ProviderIntegrationMode is “javabean” |
Activation Spec Properties
Properties in this section are specified in the sun specific deployment descriptor of MDB as activation-config-properties. All the properties specified in resource adapter section can be overridden in an ActivationSpec. Additional properties available only in ActivationSpec are given below.
|
Property Name |
Valid Values. |
Default Value. |
Description |
|---|---|---|---|
|
MaxPoolSize |
An integer |
8 |
Maximum size of server session pool internally created by resource adapter for achieving concurrent message delivery. This should be equal to maximum pool size of MDB objects. |
|
MaxWaitTime |
An integer |
3 |
Resource Adapter will wait for the time in seconds specified by this property to obtain a server session from its internal pool. If this limit is exceeded message delivery will fail. |
|
SubscriptionDurability |
“Durable” or “Non-Durable” |
“Non-Durable” |
SubscriptionDurability as specified by jms 1.1 specification. |
|
SubscriptionName |
|
NA |
SubscriptionName as specified by jms 1.1 specification. |
|
MessageSelector |
A valid message selector |
NA |
MessageSelector as specified by jms 1.1 specification. |
|
ClientID |
A valid client ID |
NA |
ClientID as specified by jms 1.1 specification. |
|
ConnectionFactoryJndiName |
A valid Jndi Name |
NA |
JNDI name of connection factory created in JMS provider. This connection factory will be used by resource adapter to create a connection to receive messages. Used only if ProviderIntegrationMode is configured as “jndi” |
|
DestinationJndiName |
A valid Jndi Name |
NA |
JNDI name of destination created in JMS provider. This destination will be used by resource adapter to create a connection to receive messages from. Used only if ProviderIntegrationMode is configured as “jndi” |
|
DestinationType |
“javax.jms.Queue” or “javax.jms.Topic” |
null (hmmm... It should be javax.jms.Queue) |
Type of the destination the MDB will listen to. |
|
DestinationProperties |
Name Value Pairs separated by comma |
NA |
This specifies the javabean propery names and values of the Destination of jms client. Required only if ProviderIntegrationMode is “javabean” |
|
RedeliveryAttempts |
integer |
|
Number of times a message will be redelivered in case a message cause a runtime exception in the MDB. |
|
RedeliveryInterval |
time in seconds |
|
interval between redeliveries, in case a message cause a runtime exception in the MDB. |
|
SendBadMessagesToDMD |
true/false |
false. |
Indicates whether RA should send the messages to a dead message destination, if redelivery attempts is exceeded. |
|
DeadMessageDestinationJndiName |
a valid JNDI name. |
NA |
JNDI name of destination created in JMS provider. Target destination for dead messages. Used only if ProviderIntegrationMode is configured as “jndi” |
|
DeadMessageDestinationClassName |
class name of destination object. |
NA |
Used if ProviderIntegrationMode is specified as “javabean” |
|
DeadMessageDestinationProperties |
Name Value Pairs separated by comma |
NA |
This specifies the javabean propery names and values of the Destination of jms client. Required only if ProviderIntegrationMode is “javabean” |
|
ReconnectAttempts |
integer |
|
Number of times a reconnect will be attempted in case exception listener catches an error on connection. |
|
ReconnectInterval |
time in seconds |
|
interval between reconnects. |
Following are the list of features implemented in the Generic Resource Adapter for JMS. More details will be given in the next version of the document.
|
Feature Name |
Description |
Comments/Caveats |
|---|---|---|
|
Connection Pooling |
The resource adapter supports connection pooling as specified by the connector specification |
|
|
Distributed Transactions |
Supports XA for both inbound and outbound communication. |
Depends on the XA support of the JMS provider and its client library. |
|
Concurrent Message Delivery |
Concurrent Message delivery for both topics and Queues. |
Batched Message delivery is not supported. |
|
Connection Exception Handling |
A CONNECTION_ERROR_OCCURED event will be sent to the application server, when a fatal error occur on a physical connection. The connection will subsequently be removed from the connection pool. |
This is an availability feature and its implementation depends on ExceptionListener support of the JMS provider. Not yet tested successfully |
|
Dead Message Destination |
After redelivering, as many times as specified in the activation-spec property RedeliveryAttempts, a poisonous message, that results in throwing of a runtime exception in a transacted MDB, will be moved to this destination |
RedeliveryAttempts and RedeliveryInterval can also be configured. |
|
Reconnect for inbound connections. |
Inbound connections will be destroyed and reconnected, if the connection that receives the messages fails |
Not yet tested successfully and depends on ExceptionListener support of the JMS provider. |
Connection Pooling cannot be used for outbound connections that use ClientID.
Load balancing of inbound messages to appserver instances of a cluster is not supported by the resource adapter. However, if a JMS provider support load balancing, resource adapter should be able to make use of that.
If the JMS client library does not support ConnectionConsumer, then inbound communication will not work.


Simpltry attempts to separate the current way of attaching behavior with a website. We think it makes more sense to add custom attributes instead of tie behavior to class names. To add a date picker to your screen simply include the appropriate libraries then add simpltry_widget="date_picker" to any div. But some objects take options. Great! Pass them through with a second attribute simpltry_options="dateString:'3/7/1979'" now your date picker will be prepopulated starting at that date.
Well like many web developers who have been personally touched (in a good way) by the web 2.0 craze, we feel that it is important to be able to easily use implement enhanced functionality. There was an article on ALA and decided that pushed us away from associating classes with functionality (it was not semantically working for a while but this confirmed it). So it was time to go down the rabbit hole, and go the route that a lot of people end up going, custom attributes. But this is expensive! Because you either mix the logic of attaching different widgets into a common place (scour the DOM once looking for all my attributes) or I had to do it over and over looking for different attributes. The ladder was just too expensive and violated the DRY philosophy that good diligent programmers strive to fulfill.
 That is why we provided an easy way to make it seem like you wrote the code yourself. All you need to do is include these three lines after the simpltry code is loaded. And fill in whatever string you like.
var YourCompany = Simpltry;
YourCompany.Widgets.widgetAttribute = "your_company_type";
YourCompany.Widgets.optionsAttribute = "your_company_options";
Then anytime you would use "simpltry_type" you would replace it with "your_company_type". The same applies to any time you would use the Simpltry object. Simpltry.DatePicker becomes YourCompany.DatePicker.
 Think they are too obtrusive? Fine. Be a purist and still use these components. Here is the complete javascript reference. Even if you don't hate widgets that will be a good reference for the options that are allowed.


Preparation time
less than 30 mins
Cooking time
10 to 30 mins
Serves
Serves 4
These simple duck and mussel mouthfuls make an ideal starter or canapé.
To make the flatbreads, place the flour, salt and coriander seeds into a large mixing bowl and gradually add water to form a dough.
Roll the dough out onto a floured surface and shape into rounds.
Heat a frying pan over a medium heat. Add the flatbreads to the pan and cook on each side for 2–3 minutes. Keep warm.
Heat a large saucepan over a medium heat. Add the mussels and wine, cover and cook for 2–3 minutes, shaking the pan occasionally.
Once the mussels have opened, strain, reserving the cooking liquor. Discard any mussels that haven’t fully opened.
Once the mussels are cool enough to handle, remove them from their shells, reserving half of the shells.
Place the fresh coriander into a small food processor with a little of the cooking liquor and blend until smooth.
Preheat the grill to high.
Lay the mussel shells on a grill tray and spoon a little of the coriander purée into each shell and top with the cooked mussel meat.
In a bowl, mix the chopped duck with the breadcrumbs.
Sprinkle the breadcrumb mix over the mussels and place under the grill for 3–5 minutes.
Brush the flatbreads with the melted butter and serve with the mussels.


Peacay, onlie begetter of the splendid BibliOdyssey site, sent me a link, saying: ‘Sometimes I see a link and they sing to me. This link sang “Hoooot Hoooooooooot Hooooooooooooting Yard”.
http://www.forgottenfutures.com/pantech/pant1.htm
I shan't spoil the occasion by describing it.’
Peacay is right. Go there and be lost in wonder and delight.


This is the offline version of the documentation. We recommend you to use the online documentation.
Sensor
Sensors use Box Colliders to detect MUs. The Sensor should be on Layer g4aSensor when the standard Game4Automation Layer settings have been used. A behavior component (e.g. Sensor_Standard) must be added to the Sensor for a connection to a PLC’s Input and Outputs.
This picture shows a configured Sensor in the demo model:
Because of limitations in the collision detection of Mesh Colliders you should always use Box Colliders with Sensors.
The Sensor can change the color by changing the material of the sensor. For this, you need to select Display Status. It is also possible to limit the sensor function to a certain Tag of the MU. You must enter the Tag in the property Limit Sensor To Tag.
The current sensor status can be inspected under the section Sensor IO’s.
Please check the Game4Automation Class Reference for more information about the properties and methods of this component.Sensor_Standard
The Sensor_Standard component provides the standard Sensor behavior and connectivity to the PLC inputs and outputs. With the property NormallyClosed=true it can be selected, as the sensor is true and the sensor is not occupied.
Please check the Game4Automation Class Reference for more information about the properties and methods of this component.The Sensor_Standard is a blueprint for additional sensors that return various values such as distance, speed etc. to the PLC. We suggest you use this template as the starting point for building your own sensors.
© 2019 in2Sight GmbH https://game4automation.com - All rights reserved. No part of this publication may be reproduced, distributed, or transmitted in any form or by any means, including printing, saving, photocopying, recording, or other electronic or mechanical methods, without the prior written permission of the publisher.


SVG
Geo-F/X's principal, Ric Wright, was one of the original members of the SVG working group, He contributed to the creation of the SVG 1.0 specification as well as Adobe's implementation of the specification, the Adobe SVG Viewer.
Even more importantly, Ric wrote most of the libraries used for import and export of SVG in all of Adobe's authoring tools, including Illustrator, InDesign ad LiveMotion. In addition, Ric was seconded to the Illustrator team for two releases, writing and testing the import/export code for two major releases of Illustrator.
Finally, Ric designed and implemented, circa 2002, a multi-paned authoring tool for SVG named Humboldt. It supported multiple views (in tabs) of the document, including WYSIWYG authoring in one tab, and an editable DOM viewable as a tree or plain text as well as a fully-functional JavaScript debugger (based on Mozilla's SpiderMonkey) with support for breakpoints and variables. Unfortunately, Adobe decided not to release Humboldt.


<%- include components/navbar-modal.html %>
<%- include components/music-modal.html %>
<%- include components/contact-modal.html %>
<%- include components/newsletter-modal.html%>
<%- include components/navbar.html %>
Music
Process
Artollo’s first album was released to
widespread critical acclaim. Mixing a
broad swath of influences Artollo ...
Heights
Artollo created a small apartment
studio as the top of a skyscraper to
record Heights. Heights explores the ...
Inside EP
Inside EP is the most visceral Artollo
project to date. This EP is a tiny explo
ration of combining Romantic Era ...


Welcome to Web Code Reader
WebCode reader is a website developed by Harun Hasić for the course Web Application Development(CS412). The websites main functionality and goal is to read and translate HTML, CSS and JavaScript code and display results in the same web page. The result is an iframe that presents the new made website. WebCode Reader can be used to learn and study HTML CSS and Javascript technologies for begginers and is a great tool to help new students easily understand these basic web languages.
How to use Web Code Reader
WebCode Reader has the ability to toggle between HTML CSS and JS. This means that you can develop with ease because You can hide your CSS or HTML or JS so that you can focus on one of the parts of your website. Following are instructions on how to use the website.
HTML
To write Your HTML code, toggle the „HTML“ button and write Your code in the window designated for HTML. Using classes and ids is recommended and You should always try to use them. Example:
CSS
To write Your CSS code that will respond to your HTML code, use the CSS window on the website. To toggle it, choose „ CSS“ button and then write code. If You want to apply some CSS to the entire webpage, write html{ *code goes here*}. For applying code to certain classes and ids, write Your css outside the html{} tag. Example:
JavaScript
To write JavaScript Code, toggle the JS button and then you can use the JavaScript window for the code. Here is an example. We will change this HTML code with a javascript function. Now we will enter javascript to change the „test“ div contents. Here is the test div in HTML:
Now we change it contents using the JavaScript.
If you have any questions and comments please email me! My email : harunze@outlook.com.


| DOSE: |
250 mg |
insufflated |
Cocaine |
(powder / crystals) |
| |
3.5 g |
smoked |
Cannabis |
(plant material) |
For the preceding year or so I had been very fascinated w/ cocaine. After seeing movies like 'Blow' and 'scarface' I was interested in the rush those people seemed to be feeling. For the previous few weeks a couple of my close friends began dabbling in cocaine.
On friday in spanish class, my friend M told me that she wanted to try to score some coke this weekend, and I told her I could try to hook it up. M had never done the drug before so we agreed to both try it for our first time together. Saturday night I was smoking a joint with some friends at a park near our homes, and M drove up with her friend K. M and I began talking about trying to get our hands on some coke, and my friend T told us he could get it. T had done coke for the first time a few days prior and really liked it. He called a friend of his and we bought a gram.
That night I snuck out with M and T, we went to a friends house where K and some guys we didn't know were hanging out. We broke up the coke and cut a few lines. T did the first while we all numbed up. I did the second, and was surprised at how easy it went in. I could feel my throat and nose tingling, and bordering on numbness. After everyone else did a line I decided to cut just one more. I blew another line and was still not feeling the 'rush' that I was seeking. I went outside for a cigarette and this was when I really started to feel the cocaine's affects, but I was still not impressed. I told myself that coke was not worth it and that I did not want to do any more.
As I came back downstairs M was cutting a few more lines and she offered me one. As much as I did not see the point in doing one more, I felt compelled to snort just one more. I snorted it, and a few minutes later I started to feel pretty pumped up. After we all chilled and talked for a while, I found myself sitting next to the table where the remainder of the coke was sitting. Without even thinking about it I began cutting another line and snorting it. After this fourth line I began to feel really high. I was more affectionate but at the same time indifferent. I felt like there was nothing that could get me down.
After finishing off the bag, we decided to head over to a friends house whose parents were away, because some of our friends were staying the night. As I walked into the house I saw my good friend A and another friend A2. A, being an experienced coke user, was interested in hearing how I liked the new experience, and how much I did. I don't remember much of this conversation, because I was too concerned over whether the house we were at had a trampoline or not. I sat down at a table with A, T, A2, M, and K where A was rolling a blunt, and we were passing a bowl around the table. Once the pot kicked in I really started to feel the extreme effects of the coke.
As we proceeded to spark the blunt in the kitchen, I began to feel very drowzy, and had the strong urge to do another line. This feeling mixed with the weed high was more enjoyable than I would expect a coke comedown to be. I almost felt drunk or like I was on DXM.  We were tricking him into saying things that made him sound like he was interested in same sex relations, and moreover began blatantly insulting him to his face. I remember finding this insanely funny and everyone cracking up over the reactions of this dipshit.
After deciding that we couldn't bare having this kid around anymore, we drove him to his brothers appartment, and drove back to the house we were at before, where A was rolling a joint. We smoked the joint and I began to feel very stoned. I felt like I had been up for days smoking pot, almost like I would never sleep again. The ever present urge to do another line was really starting to get to me, and I began to realize how people got addicted.
Around 4:45 AM I decided I needed to go home and try to chill out. I came home and layed down, taking in all my mixed feelings about the night. I was not even that impressed with coke, but at the same time had the urge to do more. I tried to sleep but ended up laying in bed and pacing around my room until 6:30 when I finally crashed out. I slept until about 9:45 and felt burned out when I woke up. I smoked a few bowls with friends that day but the burned out coke feeling was still present. Now it is about 5:45, and I feel very drowsy.
Basically the only way to sum this experience up would be with the wise words of Rick James, 'Cocaine is a hell of a drug'
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


Lunar Eclipses
thermal infrared observations
What does the Moon’s uppermost surface reveal about its space environment? To find out, we used the Air Force’s Advanced Electro Optical System (AEOS) telescope at Haleakala observatory on the summit of Maui, Hawai’i, to observe the Moon during a total lunar eclipse.
By measuring the Moon’s cooling during a -hr total eclipse, we can isolate the thermophysical properties of the uppermost mm. Thermal conductivity, porosity, and grain size all affect the cooling rates of planetary regoliths. Therefore, with the aid of models, we can measure eclipse cooling to isolate the upper layer and quantify these physical properties. Many of the Moon’s most familiar features disappear in thermal images during an eclipse, replaced by the glow of denser materials, such as small rocks in crater ejecta. Comparing the AEOS images to thermal maps from the Lunar Reconnaissance Orbiter’s Diviner instrument allows us to make inferences about the past and present rates of space weathering, impact gardening, and regolith development – important processes on many planetary bodies.
Further information:
- Hayne, P. O., Lucey, P. G., Swindle, T. R., Bandfield, J. L., Siegler, M. A., Greenhagen, B. T., & Paige, D. A. (2015, March). Thermal infrared observations of the moon during lunar eclipse using the air force Maui space surveillance system. In Lunar and Planetary Science Conference (Vol. 46, p. 1997). Link


Guidance
How researchers, third-party organisations and individuals can apply for data extracts from the national pupil database.
The national pupil database ( NPD ) contains detailed information about pupils in schools and colleges in England. The data includes:
The database also includes information about pupils’ characteristics, such as:
Subject to approval, extracts of this data are available for use by any organisation or person who, for the purpose of promoting the education or well-being of children in England are:
Information about the range of data available in the NPD , including example data, can be found in ‘ data sources by year ’ and ‘ example data files ’.
The data available in the NPD is divided into 4 tiers and can be requested in a number of different combinations:
From these tiers there are also standard data extracts available, which should fulfil most requests:
A full list of what data is available in each of the tiers and standard extracts can be found in the ‘ NPD data tables ’ and ‘ NPD user guide ’.
Bespoke extracts are available on request. A member of the NPD Data Request team will be able to advise on the approvals process, and whether the information requested is available.
The NPD is also linked to the further and higher education sectors, using data from the individualised learner record ( ILR ) and Higher Education Statistics Agency ( HESA ) student record.
You can request linked information in the following combinations:
A full list of what data is available from the ILR and HESA student record can be found in the ILR and HESA data tables .
You can contact the NPD data request team to ask:
To request extracts of the NPD or linked data you will need to complete either the ‘ NPD data request application form ’ or ‘Linked data request application form’ and ‘ Information security questionnaire ’.
You should fill in these forms electronically and email them to the NPD data request team.
You will have to demonstrate that you comply with all relevant requirements of the Data Protection Act 1998 , including proving that you or your organisation:
For any tier 1 or 2 requests, each individual user of the data must also provide a copy of a ‘basic disclosure’ certificate that is no more than 2 years old. You can get this certificate from Disclosure Scotland . We will also accept more detailed disclosure certificates, but please be aware that we will take all the evidence in the certificate into account before making a decision.
Contact the NPD team or use the contact us form to make a request.
Please be as specific as you can about the data you’re asking about.
You’ll need to confirm your identity - we’ll usually ask you to send documents proving your name and address.
There are different approval processes depending on the sensitivity and types of data extract you request.
Requests for extracts from tier 1 can only be approved by our Data Management Advisory panel. In these cases applicants must also give line-by-line explanations for why each sensitive item is required, and why the same outcome cannot be achieved using less sensitive data.
Requests for extracts from tiers 2, 3 and 4, will be dealt with by the NPD Data Request team.
We administer all requests for linked data, but these are referred to:
These bodies will consider your request, and will communicate their decisions to us, including specifying any conditions for the release of their data.
We will inform you of all decisions relating to the release of NPD or linked data.
If we need more information, we will ask you to provide this. We will also give feedback explaining reasons why we have rejected a request.
If your application is approved you will be required to sign a licence agreement and provide completed individual declarations for each named user of the data.
Once we receive the signed agreement, and any user declaration forms, the requested data will be transferred securely.
The data will be encrypted and the password will only be released to the named person in the application pack.
There are exemptions in the Data Protection Act to an organisation’s duty to supply personal data. In some cases, we may withhold some or all of the personal data you request about yourself or your family.
All NPD and linked data request application forms and downloads, including the ‘ National pupil database user guide ’ and example data sets are available on the National pupil database: document collection .
Published: 25 March 2014
Updated: 29 April 2016
From: Department for Education


| 100,253 | 67,890 | 2,567 | 169,000 | ||
|
Total
|
| 100,253 | 67,890 | 2,567 | 169,000 | ||
|
Total
|
| 100,253 | 67,890 | 2,567 | 169,000 | ||
|
Total
|


Money Play. How should Red play 66?
pips Red=178 White=142
(CorrectAnswer= 0/0, ErrorScore= 0)
Over the board 24/18, 21/3 was played but that is an error.
The idea is to get more of those rear checkers moving to contest the outer boards. There are two candidate plays, 21/9(2) and 21/15, 21/3. They both expose the remaining checkers to attack but that is compensated for by the stronger forward position that Red establishes.
This is not an easy problem because it looks as if Red should hold on to the 21-pt, but the rollouts show clearly that this is not the case. For once giving up an anchor is correct.
The idea is to get more of those rear checkers moving to contest the outer boards. There are two candidate plays, 21/9(2) and 21/15, 21/3. They both expose the remaining checkers to attack but that is compensated for by the stronger forward position that Red establishes.
This is not an easy problem because it looks as if Red should hold on to the 21-pt, but the rollouts show clearly that this is not the case. For once giving up an anchor is correct.
1. Cubeful 2-ply 21/9(2) Eq.: -0.219 0.441 0.133 0.006 - 0.559 0.155 0.010 2. Cubeful 2-ply 21/3 21/15 Eq.: -0.225 (-0.006) 0.437 0.131 0.006 - 0.563 0.153 0.009 3. Cubeful 2-ply 24/18 21/3 Eq.: -0.249 (-0.030) 0.420 0.111 0.004 - 0.580 0.115 0.004 4. Cubeful 2-ply 21/3 13/7 Eq.: -0.278 (-0.059) 0.412 0.120 0.005 - 0.588 0.126 0.004 5. Cubeful 2-ply 21/9 21/15(2) Eq.: -0.313 (-0.094) 0.420 0.115 0.005 - 0.580 0.173 0.010


| HostNameProperty | The key into the Properties map for the host name value. |
| IdentityProperty | The key into the Properties map for the thread identity value. |
| UserNameProperty | The key into the Properties map for the user name value. |
| StartTime | Gets the time when the current process started. |
| LoggingEvent | Overloaded. Initializes a new instance of the LoggingEvent class. |
| Domain | Gets the AppDomain friendly name. |
| ExceptionObject | Gets the exception object used to initialize this event. |
| Fix | The fixed fields in this event |
| Identity | Gets the identity of the current thread principal. |
| Level | Gets the Level of the logging event. |
| LocationInformation | Gets the location information for this logging event. |
| LoggerName | Gets the name of the logger that logged the event. |
| MessageObject | Gets the message object used to initialize this event. |
| Properties | Additional event specific properties. |
| RenderedMessage | Gets the message, rendered through the RendererMap. |
| Repository | The ILoggerRepository that this event was created in. |
| ThreadName | Gets the name of the current thread. |
| TimeStamp | Gets the time of the logging event. |
| UserName | Gets the name of the current user. |
| Equals (inherited from Object) | Determines whether the specified Object is equal to the current Object. |
| FixVolatileData | Overloaded. Fix instance fields that hold volatile data. |
| GetExceptionString | Returns this event's exception's rendered using the RendererMap. |
| GetExceptionStrRep | Obsolete. Returns this event's exception's rendered using the RendererMap. |
| GetHashCode (inherited from Object) | Serves as a hash function for a particular type, suitable for use in hashing algorithms and data structures like a hash table. |
| GetLoggingEventData | Overloaded. Gets the portable data for this LoggingEvent. |
| GetObjectData | Serializes this object into the SerializationInfo provided. |
| GetProperties | Get all the composite properties in this event |
| GetType (inherited from Object) | Gets the Type of the current instance. |
| LookupProperty | Lookup a composite property in this event |
| ToString (inherited from Object) | Returns a String that represents the current Object. |
| WriteRenderedMessage | Write the rendered message to a TextWriter |
| LoggingEvent | Overloaded. Initializes a new instance of the LoggingEvent class. |
| Finalize (inherited from Object) | Allows an Object to attempt to free resources and perform other cleanup operations before the Object is reclaimed by garbage collection. |
| FixVolatileData | Overloaded. Fix the fields specified by the FixFlags parameter |
| MemberwiseClone (inherited from Object) | Creates a shallow copy of the current Object. |
LoggingEvent Class | log4net.Core Namespace


Raw level automatically awarded GB final
This data has achieved Raw level on 28 October 2014 which means this data makes a great start at the basics of publishing open data.
Ashfield Planning Applications
Summary
- Type of release
- a one-off release of a single dataset
- Licence
- Open Government Licence 2.0 (United Kingdom)
- Verification
- automatically awarded
- Release Date
- 15 October 2014
- Modified Date
- 22 October 2014
Publishers
Licenses
Keywords
- development., planning
Temporal Coverage
- 1974-01-012013-12-31
- temporal_coverage
Community verification
Other people can verify whether the answers on this certificate are correct.
This certificate is automatically awarded.
Sign in to verify or report this certificate
Description
Historic planning applications in the district of Ashfield released under the LG Open Data Incentive Scheme. Data shows planning reference, date, location, description, decision date and decision.
General Information
-
This data is described at
http://data.gov.uk/dataset/ashfield-planing-applications Do you think this data is incorrect? Let us know
-
This data is published by
Ashfield District Council Do you think this data is incorrect? Let us know
Legal Information
-
This data was
originally created or generated by its curator Do you think this data is incorrect? Let us know
-
The rights statement is at
http://data.gov.uk/dataset/ashfield-planing-applications Do you think this data is incorrect? Let us know
-
This data is available under
UK Open Government Licence Do you think this data is incorrect? Let us know
-
The content is available under
UK Open Government Licence Do you think this data is incorrect? Let us know
-
This data contains
no data about individuals Do you think this data is incorrect? Let us know
Practical Information
-
The data appears in this collection
http://data.gov.uk Do you think this data is incorrect? Let us know
Technical Information
-
This data is
machine-readable Do you think this data is incorrect? Let us know
-
The format of this data is
a standard open format Do you think this data is incorrect? Let us know
Social Information
-
The documentation includes machine-readable data for
title Do you think this data is incorrect? Let us know
-
The documentation includes machine-readable data for
description Do you think this data is incorrect? Let us know
-
The documentation includes machine-readable data for
publisher Do you think this data is incorrect? Let us know
-
The documentation includes machine-readable data for
keyword(s) or tag(s) Do you think this data is incorrect? Let us know
-
The documentation includes machine-readable data for
distribution(s) Do you think this data is incorrect? Let us know
-
The documentation includes machine-readable data for
release date Do you think this data is incorrect? Let us know
-
The documentation includes machine-readable data for
modification date Do you think this data is incorrect? Let us know
-
The documentation includes machine-readable data for
temporal coverage Do you think this data is incorrect? Let us know


Simulink CPI interface
Home > User Guides
Simulink library
MFeval blocks are available from the Simulink library (mfeval_LIB.slx). Four masks and two interfaces (CPI and STI) are
available to the user (see figure below):
CPI tyre model
The Contact Point Interface (shown below) evaluates the Magic Formula in the contact point between the tire and the road.
Therefore, the CPI interface does not describe the entire vertical dynamics of the tire (effects like vertical damping are not modelled)
The outputs are forces and moments defined in the contact point, i.e. the magic formula outputs without any translation or rotation.
W-axis system
The coordinate system used in a CPI tire model is the W-axis system defined by the TYDEX group.
- The XW-axis is given by the intersection of the central plane of the wheel with the track surface.
- The YW-axis is given by the projection of the spin axis onto the ground.
- The ZW-axis is normal to the ground and points upwards.
- The origin of the W-axis system is also called "wheel intersection point" in the TYDEX-Reference Manual.
Note: The W-axis system (wheel axis system) is standardized in ISO 8855. In ISO, the track surface is
defined as horizontal (horizontal plane = ground plane), but in this TYDEX Axis System also a sloped
ground is permissible.
- Forces and moments shown are acting from tire to rim.
- Slip angle (alpha) shown is positive.
- Inclination angle (gamma) shown is positive.
- Wheel angular velocity (omega) shown is positive.
Inputs
| Input name |
Dimension |
Description |
Units |
| Omega |
(1) |
Wheel rotational speed about wheel spin axis |
(rad/s) |
| Vx |
(1) |
Forward velocity of wheel center in the wheel plane, parallel to the road surface |
(m/s) |
| Vsy |
(1) |
Lateral wheel slip velocity at the tire-road contact point |
(m/s) |
| Camber |
(1) |
Inclination angle of the wheel with respect to the road |
(m/s) |
| Psidot |
(1) |
Tyre yaw velocity about the road normal. (Steering ratio at zero speed) |
(rad/s) |
| Fz |
(1) |
Tyre normal load in the contact point |
(N) |
| muRoad |
(1) |
Friction coefficient between the tire and the road. (Set to 1 if unknown) |
(-) |
Outputs
| Output name |
Dimension |
Description |
Units |
| Fx |
(1) |
Tyre longitudinal force in the tire-road contact point |
(N) |
| Fy |
(1) |
Tyre lateral force in the tire-road contact point |
(N) |
| Fz |
(1) |
Tyre vertical force in the tire-road contact point (bypass from inputs) |
(N) |
| Mx |
(1) |
Tyre overturning moment in the tire-road contact point |
(Nm) |
| My |
(1) |
Tyre rolling resistance moment |
(Nm) |
| Mz |
(1) |
Tyre self aligning moment in the tire-road contact point |
(Nm) |
| varinf |
(27) |
Various useful signals from the model (SA, SR, Rl, etc). Use the bus selector to explore |
(-) |
Mask interface
There are two types of Mask interfaces: dropdown menu and programmable.
If the user double clicks on the "Dropwdown menu" block the mask will pop-out an interface as shown below:
Similarly if the user double clicks on the "Programmable" block the mask will pop-out an interface as shown below:
There are 4 parameters that the user has to specify:
- The location of the TIR file: This can be a string pointing to the file location or a structure generated with mfeval.loadTIR.
- Tyre side: Choose between Left or Right. Depending on the tyre side selected, the lateral force (Fy), the self-aligning torque (Mz) and the overturning moment (Mx) will be mirrored.
- Dynamics: Choose between Steady State, Linear Transients or Non-linear Transients. Read the paper from Besselink for more information.
- Use mode: Choose between Combined or Combined+Turn-slip. Turn-slip effects are only relevant when turning at short turning radii and low speed.
And 1 optional parameter:
- The tire inflation pressure in bar: if the check-box is not activated, the model will be solved with the pressure specified in the .tir file with the parameter INFLPRES. Note that this parameter will only affect to Magic Formula 6.1 or above versions.
Solver Settings
All MFeval blocks can be used with variable-step or fixed-step solvers:
- If a variable-step solver is used the solver will automatically determine the correct time step. For transient simulations (slip angle rate > 10 deg/s) it is recommended to use the solver ode23t (mod. stiff/Trapezoidal).
- If a fixed-step solver is used the user needs to ensure that the time step is small enough to keep the simulation stable.
The recommended step sizes for each Dynamic mode are:
i) Steady-state <= 0.01 seconds
ii) Linear relaxation lengths <=0.001 seconds
iii) Non-linear relaxation lengths <= 0.00025 seconds
Example/Demo
There is a demo file (demo_cpi.slx) showing how to use the CPI block in the installation folder under: doc > examples.
Type "open('demo_cpi.slx')" in the command window to open the model.
Known issues
- When running the model with transient dynamics and fixed-step solvers, the time step should be at least 0.00025 seconds. This may change depending on the inputs, but if the output forces are instable try to decrease the time-step.
- The model is only valid up to 10 Hz of the tyre dynamic excitation if using transient dynamics (linear or non-linear).
- Parking efforts are not included.
- Turn-slip equations have not been validated. Note that turn-slip (3rd slip input) is only relevant at low speeds (e.g. parking maneuvers)
- When using MF6.2, the loaded radius output is the same as for the MF6.1 model (with no camber effects) due to the increasing computational power required.


Please type some keys and see what happens. Try typing key modifiers at the same time: shift, alt, control


--- layout: page title: 404 permalink: /404.html group: Cresspresso order: 0 hide: true ---
The page you were searching for could not be found (it does not exist or has been moved).


| Review Number | Reviewer | Restaurant | Restaurant Location | Date | Description | Rating (1-5) |
Would Recommend |
|---|---|---|---|---|---|---|---|
| 1 | {{ reviewer.name }} | {{ restaurant.name }} | {{ restaurant.address }} | {{ review.date }} | {{ review.partial }} (Full review) | 4 | Yes |


|
Xenomai
3.0.4
|
A programming interface reminiscent from traditional RTOS APIs. More...
Modules | |
| Alarm services | |
| General-purpose watchdog timers. | |
| Buffer services | |
| Lightweight FIFO IPC mechanism. | |
| Condition variable services | |
| POSIXish condition variable mechanism. | |
| Event flag group services | |
| Inter-task notification mechanism based on discrete flags. | |
| Heap management services | |
| Region of memory dedicated to real-time allocation. | |
| Mutex services | |
| POSIXish mutual exclusion servicesl. | |
| Message pipe services | |
| Two-way communication channel between Xenomai & Linux domains. | |
| Message queue services | |
| real-time IPC mechanism for sending messages of arbitrary size | |
| Semaphore services | |
| Counting semaphore IPC mechanism. | |
| Task management services | |
| Services dealing with preemptive multi-tasking. | |
| Timer management services | |
| Services for reading and spinning on the hardware timer. | |
A programming interface reminiscent from traditional RTOS APIs.
This interface is an evolution of the former native API available with the Xenomai 2.x series.


HTML 4.01 快速参考
HTML 4.01 快速参考
HTML Basic Document
  <title>Document name goes here</title>   Visible text goes here
Text Elements

This is a paragraph

 (line break)
 (horizontal rule)
This text is preformatted

This is a paragraph
(line break)
(horizontal rule)
This text is preformatted
Logical Styles
This text is emphasized This text is strong This is some computer codeThis text is emphasized This text is strong
This is some computer code
Physical Styles
This text is bold This text is italicThis text is bold This text is italic
Links, Anchors, and Image Elements
This is a Link  <a<EMAIL_ADDRESS>e-mailA named anchor: Useful Tips Section Jump to the Useful Tips SectionThis is a Link Send e-mailA named anchor: Useful Tips Section Jump to the Useful Tips Section
Unordered list

First item

Next item

- First item
- Next item
Ordered list

First item

Next item

- First item
- Next item
Definition list

First term

Definition

Next term

Definition

- First term
- Definition
- Next term
- Definition
Tables

 someheader	 someheader

 sometext	 sometext

| someheader | someheader |
|---|---|
| sometext | sometext |
Frames
<frameset cols="25%,75%"> <frame src="page1.htm"> <frame src="page2.htm"> </frameset>
Forms
<form action="http://www.example.com/test.asp" method="post/get"> <input type="text" name="lastname" value="Nixon" size="30" maxlength="50"> <input type="password"> <input type="checkbox" checked="checked"> <input type="radio" checked="checked"> <input type="submit"> <input type="reset"> <input type="hidden"> <select> <option>Apples <option selected>Bananas <option>Cherries </select> <textarea name="Comment" rows="10"cols="20"></textarea> </form>
Entities
< is the same as < > is the same as > © is the same as ©< is the same as < > is the same as > © is the same as ©
Other Elements

 Text quoted from some source.
 <address> Address 1
 Address 2
 City
 </address>
Text quoted from some source.Address 1
Address 2
City


Functions |
| bStatus_t | GATT_InitServer (void) |
| | Initialize the Generic Attribute Profile Server.
|
| bStatus_t | GATT_RegisterService (gattService_t *pService) |
| | Register a service attribute list with the GATT Server. A service is composed of characteristics or references to other services. Each characteristic contains a value and may contain optional information about the value. There are two types of services: primary service and secondary service.
|
| bStatus_t | GATT_DeregisterService (uint16 handle, gattService_t *pService) |
| | Deregister a service attribute list with the GATT Server.
|
| void | GATT_RegisterForReq (uint8 taskId) |
| | Register to receive incoming ATT Requests.
|
| bStatus_t | GATT_VerifyReadPermissions (uint16 connHandle, uint8 permissions) |
| | Verify the permissions of an attribute for reading.
|
| bStatus_t | GATT_VerifyWritePermissions (uint16 connHandle, uint8 permissions, attWriteReq_t *pReq) |
| | Verify the permissions of an attribute for writing.
|
| uint8 | GATT_ServiceChangedInd (uint16 connHandle, uint8 taskId) |
| | Send out a Service Changed Indication.
|
| gattAttribute_t * | GATT_FindHandleUUID (uint16 startHandle, uint16 endHandle, const uint8 *pUUID, uint16 len, uint16 *pHandle) |
| | Find the attribute record for a given handle and UUID.
|
| gattAttribute_t * | GATT_FindHandle (uint16 handle, uint16 *pHandle) |
| | Find the attribute record for a given handle.
|
| gattAttribute_t * | GATT_FindNextAttr (gattAttribute_t *pAttr, uint16 endHandle, uint16 service, uint16 *pLastHandle) |
| | Find the next attribute of the same type for a given attribute.
|
| uint16 | GATT_ServiceNumAttrs (uint16 handle) |
| | Get the number of attributes for a given service.
|
Register a service attribute list with the GATT Server. A service is composed of characteristics or references to other services. Each characteristic contains a value and may contain optional information about the value. There are two types of services: primary service and secondary service.
A service definition begins with a service declaration and ends before the next service declaration or the maximum Attribute Handle.
A characteristic definition begins with a characteristic declaration and ends before the next characteristic or service declaration or maximum Attribute Handle.
The attribute server will only keep a pointer to the attribute list, so the calling application will have to maintain the code and RAM associated with this list.
- Parameters:
-
| pService | - pointer to service attribute list to be registered |
- Returns:
- SUCCESS: Service registered successfully.
INVALIDPARAMETER: Invalid service field.
FAILURE: Not enough attribute handles available.
bleMemAllocError: Memory allocation error occurred.


real operating system
`Prev `__
R
`Next `__
--------------
**real operating system**: n.
The sort the speaker is used to. People from the BSDophilic academic
community are likely to issue comments like “System V? Why don't you use
a *real* operating system?”, people from the commercial/industrial Unix
sector are known to complain “BSD? Why don't you use a *real* operating
system?”, and people from IBM object “Unix? Why don't you use a *real*
operating system?” Only `*MS-DOS* <../M/MS-DOS.html>`__ is universally
considered unreal. See `*holy wars* <../H/holy-wars.html>`__,
`*religious issues* `__,
`*proprietary* <../P/proprietary.html>`__, `*Get a real
computer!* <../G/Get-a-real-computer-.html>`__
--------------
+------------------------------+----------------------------+------------------------------------+
| `Prev `__ | `Up <../R.html>`__ | `Next `__ |
+------------------------------+----------------------------+------------------------------------+
| real hack | `Home <../index.html>`__ | Real Programmer |
+------------------------------+----------------------------+------------------------------------+


Generic CAPTCHA solver.
| Field | Type | Label | Description |
| solver_id | bytes | optional |
|
| name | string | optional |
|
| created_at | string | optional |
|
| updated_at | string | optional |
|
| antigate | CaptchaSolverAntigate | optional |
|
CAPTCHA solver for Antigate-compatible API.
| Field | Type | Label | Description |
| service_url | string | optional |
|
| api_key | string | optional |
|
| require_phrase | bool | optional |
|
| case_sensitive | bool | optional |
|
| characters | CaptchaSolverAntigateCharacters | optional |
|
| require_math | bool | optional |
|
| min_length | int32 | optional |
|
| max_length | int32 | optional |
|
Contains a crawl response, i.e. something downloaded by the crawler or the error/exception that resulted from attempting to download it.
| Field | Type | Label | Description |
| body | bytes | optional |
|
| completed_at | string | optional |
|
| content_type | string | optional |
|
| cost | double | optional |
|
| duration | double | optional |
|
| exception | string | optional |
|
| headers | Header | repeated |
|
| is_compressed | bool | optional |
|
| is_success | bool | optional |
|
| job_id | bytes | optional |
|
| started_at | string | optional |
|
| status_code | int32 | optional |
|
| url | string | optional |
|
| url_can | string | optional |
|
Login information for a domain.
| Field | Type | Label | Description |
| domain | string | optional |
|
| login_url | string | optional |
|
| login_test | string | optional |
|
| users | DomainLoginUser | repeated |
|
Username/password for a domain.
| Field | Type | Label | Description |
| username | string | optional |
|
| password | string | optional |
|
| working | bool | optional |
|
An Event is sent for any active subscription whenever data is available for that subscription.
| Field | Type | Label | Description |
| subscription_id | int32 | required |
|
| job_list | JobList | optional |
|
| schedule_list | ScheduleList | optional |
|
| resource_frame | ResourceFrame | optional |
|
| subscription_closed | SubscriptionClosed | optional |
|
| sync_item | SyncItem | optional |
|
| task_tree | TaskTree | optional |
|
An HTTP header.
| Field | Type | Label | Description |
| key | string | optional |
|
| value | string | optional |
|
A crawl job.
| Field | Type | Label | Description |
| job_id | bytes | required |
|
| seeds | string | repeated |
|
| policy | Policy | optional |
|
| name | string | optional |
|
| tags | string | repeated |
|
| run_state | JobRunState | optional |
|
| started_at | string | optional |
|
| completed_at | string | optional |
|
| item_count | int32 | optional | Default: -1 |
| http_success_count | int32 | optional | Default: -1 |
| http_error_count | int32 | optional | Default: -1 |
| exception_count | int32 | optional | Default: -1 |
| http_status_counts | Job.HttpStatusCountsEntry | repeated |
|
| Field | Type | Label | Description |
| key | int32 | optional |
|
| value | int32 | optional |
|
A list of jobs.
This seemingly stupid message is necessary so that a list of jobs can be used as the body of a "oneof".
| Field | Type | Label | Description |
| jobs | Job | repeated |
|
For paginating large sets.
| Field | Type | Label | Description |
| limit | int32 | optional | Default: 10 |
| offset | int32 | optional |
|
Performance profile data for a single function.
| Field | Type | Label | Description |
| file | string | optional |
|
| line_number | int32 | optional |
|
| function | string | optional |
|
| calls | int32 | optional |
|
| non_recursive_calls | int32 | optional |
|
| total_time | double | optional |
|
| cumulative_time | double | optional |
|
Settings that dictate crawler behavior. Policy is set on a job-by-job basis.
| Field | Type | Label | Description |
| policy_id | bytes | optional |
|
| name | string | optional |
|
| created_at | string | optional |
|
| updated_at | string | optional |
|
| captcha_solver_id | bytes | optional |
|
| authentication | PolicyAuthentication | optional |
|
| limits | PolicyLimits | optional |
|
| proxy_rules | PolicyProxyRule | repeated |
|
| mime_type_rules | PolicyMimeTypeRule | repeated |
|
| robots_txt | PolicyRobotsTxt | optional |
|
| url_normalization | PolicyUrlNormalization | optional |
|
| url_rules | PolicyUrlRule | repeated |
|
| user_agents | PolicyUserAgent | repeated |
|
Settings for authenticated crawling.
| Field | Type | Label | Description |
| enabled | bool | optional |
|
Specifies limits on how far or how long a crawl runs.
| Field | Type | Label | Description |
| max_cost | double | optional |
|
| max_duration | double | optional |
|
| max_items | int32 | optional |
|
Specifies whether to save or discard certain responses based on MIME type.
If pattern is not specified, then this rule applies to all responses.
| Field | Type | Label | Description |
| pattern | string | optional |
|
| match | PatternMatch | optional |
|
| save | bool | optional |
|
When and how to proxy requests.
| Field | Type | Label | Description |
| pattern | string | optional |
|
| match | PatternMatch | optional |
|
| proxy_url | string | optional |
|
Specify handling of robots.txt.
| Field | Type | Label | Description |
| usage | PolicyRobotsTxt.Usage | required |
|
| Field | Type | Label | Description |
| enabled | bool | optional |
|
| strip_parameters | string | repeated |
|
A rule for adjusting a URL's cost.
| Field | Type | Label | Description |
| pattern | string | optional |
|
| match | PatternMatch | optional |
|
| action | PolicyUrlRule.Action | optional |
|
| amount | double | optional |
|
Specifies a user agent string to send when downloading a resource.
| Field | Type | Label | Description |
| name | string | required |
|
Model for a rate limit.
If domain is not specified, the global rate limit is modified. If delay is not specified, then the rate limit for the specified domain is deleted. Either delay or domain must be specified: you are not allowed to delete the global limit.
If the client sends a name, the server ignores it. The server will always send a name to the client.
| Field | Type | Label | Description |
| name | string | optional |
|
| delay | float | optional |
|
| token | bytes | optional |
|
| domain | string | optional |
|
A Request is issued by the client, and the server is expected to send exactly 1 Response for each Request.
| Field | Type | Label | Description |
| request_id | int32 | required | The request ID is included in the response so that the client can correlate requests and responses. (Responses may arrive in a different order than the requests were sent.) |
| delete_captcha_solver | RequestDeleteCaptchaSolver | optional |
|
| get_captcha_solver | RequestGetCaptchaSolver | optional |
|
| list_captcha_solvers | RequestListCaptchaSolvers | optional |
|
| set_captcha_solver | RequestSetCaptchaSolver | optional |
|
| delete_job | RequestDeleteJob | optional |
|
| get_job | RequestGetJob | optional |
|
| get_job_items | RequestGetJobItems | optional |
|
| list_jobs | RequestListJobs | optional |
|
| set_job | RequestSetJob | optional |
|
| delete_schedule | RequestDeleteSchedule | optional |
|
| get_schedule | RequestGetSchedule | optional |
|
| list_schedules | RequestListSchedules | optional |
|
| list_schedule_jobs | RequestListScheduleJobs | optional |
|
| set_schedule | RequestSetSchedule | optional |
|
| delete_policy | RequestDeletePolicy | optional |
|
| get_policy | RequestGetPolicy | optional |
|
| list_policies | RequestListPolicies | optional |
|
| set_policy | RequestSetPolicy | optional |
|
| delete_domain_login | RequestDeleteDomainLogin | optional |
|
| get_domain_login | RequestGetDomainLogin | optional |
|
| list_domain_logins | RequestListDomainLogins | optional |
|
| set_domain_login | RequestSetDomainLogin | optional |
|
| list_rate_limits | RequestListRateLimits | optional |
|
| set_rate_limit | RequestSetRateLimit | optional |
|
| performance_profile | RequestPerformanceProfile | optional |
|
| subscribe_job_status | RequestSubscribeJobStatus | optional |
|
| subscribe_job_sync | RequestSubscribeJobSync | optional |
|
| subscribe_resource_monitor | RequestSubscribeResourceMonitor | optional |
|
| subscribe_task_monitor | RequestSubscribeTaskMonitor | optional |
|
| unsubscribe | RequestUnsubscribe | optional |
|
Delete a CAPTCHA solver.
| Field | Type | Label | Description |
| solver_id | bytes | optional |
|
Delete a credential and all of its passwords.
| Field | Type | Label | Description |
| domain | string | optional |
|
Delete a job and all of its items.
| Field | Type | Label | Description |
| job_id | bytes | required |
|
Delete a policy.
| Field | Type | Label | Description |
| policy_id | bytes | required |
|
Delete a job schedule.
| Field | Type | Label | Description |
| schedule_id | bytes | required |
|
Get a CAPTCHA solver by ID.
| Field | Type | Label | Description |
| solver_id | bytes | required |
|
Get credential data for the specified domain.
| Field | Type | Label | Description |
| domain | string | required |
|
Get metadata for the specified job.
| Field | Type | Label | Description |
| job_id | bytes | required |
|
Get a list of items (crawl responses) from a job.
| Field | Type | Label | Description |
| job_id | bytes | required |
|
| include_success | bool | optional |
|
| include_error | bool | optional |
|
| include_exception | bool | optional |
|
| compression_ok | bool | optional | Default: true |
| page | Page | optional |
|
Get a policy.
| Field | Type | Label | Description |
| policy_id | bytes | required |
|
Get metadata for the specified job schedule.
| Field | Type | Label | Description |
| schedule_id | bytes | required |
|
Get a list of CAPTCHA solvers.
| Field | Type | Label | Description |
| page | Page | optional |
|
Get a list of domain logins.
| Field | Type | Label | Description |
| page | Page | optional |
|
Get a list of jobs.
| Field | Type | Label | Description |
| page | Page | optional |
|
| started_after | string | optional |
|
| tag | string | optional |
|
| schedule_id | bytes | optional |
|
Get a list of policies.
| Field | Type | Label | Description |
| page | Page | optional |
|
Show rate limits.
| Field | Type | Label | Description |
| page | Page | optional |
|
Get a list of jobs for a given schedules.
| Field | Type | Label | Description |
| schedule_id | bytes | required |
|
| page | Page | optional |
|
Get a list of job schedules.
| Field | Type | Label | Description |
| page | Page | optional |
|
Request a performance profile.
| Field | Type | Label | Description |
| duration | double | optional | Default: 5 |
| sort_by | string | optional | Default: total_time |
| top_n | int32 | optional |
|
Create or modify a CAPTCHA solver.
| Field | Type | Label | Description |
| solver | CaptchaSolver | optional |
|
Add or update metadata for a domain login.
| Field | Type | Label | Description |
| login | DomainLogin | optional |
|
Create a job or update state for an existing job.
Name, seeds, tags, and policy may only be specified for new jobs. Once a job is created, only the run state may be changed.
| Field | Type | Label | Description |
| job_id | bytes | optional |
|
| run_state | JobRunState | optional |
|
| policy_id | bytes | optional |
|
| seeds | string | repeated |
|
| name | string | optional |
|
| tags | string | repeated |
|
Create or update a crawl policy.
If the policy's ID is blank, then the server will create a new policy. If the ID is not blank, then the server will update the corresponding policy.
| Field | Type | Label | Description |
| policy | Policy | required |
|
Set a rate limit.
| Field | Type | Label | Description |
| domain | string | optional |
|
| delay | float | optional |
|
Create or update a job schedule.
| Field | Type | Label | Description |
| schedule | Schedule | optional |
|
Subscribe to job status, e.g. run state, statistics, etc.
| Field | Type | Label | Description |
| min_interval | double | optional | The minimum amount of time between jobs status messages. If multiple job statuses change in rapid succession, those changes are coalesced into a single event. Default: 1 |
Synchronize crawl responses.
| Field | Type | Label | Description |
| job_id | bytes | required |
|
| sync_token | bytes | optional |
|
| compression_ok | bool | optional | Default: true |
Subscribe to resource monitoring, e.g. CPU usage, memory usage, downloads/sec, etc.
| Field | Type | Label | Description |
| history | int32 | optional | Default: 300 |
Subscribe to updates about resource usage (CPU, memory, disk, etc.)
| Field | Type | Label | Description |
| period | double | optional | Default: 3 |
| top_n | int32 | optional | Default: 20 |
Close the specified subscription.
| Field | Type | Label | Description |
| subscription_id | int32 | required |
|
Data about resource consumption.
| Field | Type | Label | Description |
| timestamp | string | optional |
|
| cpus | ResourceFrameCpu | repeated |
|
| memory | ResourceFrameMemory | optional |
|
| disks | ResourceFrameDisk | repeated |
|
| networks | ResourceFrameNetwork | repeated |
|
| jobs | ResourceFrameJob | repeated |
|
| current_downloads | int32 | optional |
|
| maximum_downloads | int32 | optional |
|
| rate_limiter | int32 | optional |
|
CPU usage.
| Field | Type | Label | Description |
| usage | double | optional |
|
Disk usage.
| Field | Type | Label | Description |
| mount | string | optional |
|
| used | int64 | optional |
|
| total | int64 | optional |
|
Resources used by a crawl job.
| Field | Type | Label | Description |
| job_id | bytes | optional |
|
| name | string | optional |
|
| current_downloads | int32 | optional |
|
Memory usage.
| Field | Type | Label | Description |
| used | int64 | optional |
|
| total | int64 | optional |
|
Network usage.
| Field | Type | Label | Description |
| name | string | optional |
|
| sent | int64 | optional |
|
| received | int64 | optional |
|
The server sends exactly one Response for each Request it receives.
| Field | Type | Label | Description |
| request_id | int32 | required | The request ID will match the request that prompted this response. |
| is_success | bool | required |
|
| error_message | string | optional |
|
| solver | CaptchaSolver | optional |
|
| new_solver | ResponseNewCaptchaSolver | optional |
|
| list_captcha_solvers | ResponseListCaptchaSolvers | optional |
|
| domain_login | DomainLogin | optional |
|
| domain_login_user | DomainLoginUser | optional |
|
| list_domain_logins | ResponseListDomainLogins | optional |
|
| job | Job | optional |
|
| new_job | ResponseNewJob | optional |
|
| list_items | ResponseListItems | optional |
|
| list_jobs | ResponseListJobs | optional |
|
| schedule | Schedule | optional |
|
| new_schedule | ResponseNewSchedule | optional |
|
| list_schedules | ResponseListSchedules | optional |
|
| list_schedule_jobs | ResponseListScheduleJobs | optional |
|
| policy | Policy | optional |
|
| new_policy | ResponseNewPolicy | optional |
|
| list_policies | ResponseListPolicies | optional |
|
| list_rate_limits | ResponseListRateLimits | optional |
|
| new_subscription | ResponseNewSubscription | optional |
|
| performance_profile | ResponsePerformanceProfile | optional |
|
Return a list of CAPTCHA solvers.
| Field | Type | Label | Description |
| solvers | CaptchaSolver | repeated |
|
| total | int32 | optional | The total number of solvers (not the count of solvers included in this response). |
Return a list of domain logins.
| Field | Type | Label | Description |
| logins | DomainLogin | repeated |
|
| total | int32 | optional | The total number of domains (not the count of domains included in this response). |
Return a list of items (crawl responses) for a job.
| Field | Type | Label | Description |
| items | CrawlResponse | repeated |
|
| total | int32 | optional | The total number of items (not the count of items included in this response). |
Return a list of jobs.
| Field | Type | Label | Description |
| jobs | Job | repeated |
|
| total | int32 | optional | The total number of jobs (not the count of jobs included in this response). |
Return a list of jobs.
| Field | Type | Label | Description |
| policies | Policy | repeated |
|
| total | int32 | optional | The total number of jobs (not the count of jobs included in this response). |
Return a list of rate limits.
| Field | Type | Label | Description |
| rate_limits | RateLimit | repeated |
|
| total | int32 | optional | The total number of rate limits (not the count of rate limits included in this response). |
Return a list of jobs for a given schedules.
| Field | Type | Label | Description |
| jobs | Job | repeated |
|
| total | int32 | optional | The total number of jobs associated with this schedule (not just the ones included in this response). |
Return a list of job schedules.
| Field | Type | Label | Description |
| schedules | Schedule | repeated |
|
| total | int32 | optional | The total number of job schedules (not just the ones included in this response). |
A response containing the ID of a newly created CAPTCHA solver.
| Field | Type | Label | Description |
| solver_id | bytes | required |
|
A response containing the ID of a newly created job.
| Field | Type | Label | Description |
| job_id | bytes | required |
|
A response containing the ID of a newly created policy.
| Field | Type | Label | Description |
| policy_id | bytes | required |
|
A response containing the ID of a newly created job schedule.
| Field | Type | Label | Description |
| schedule_id | bytes | required |
|
A response containing the ID of a newly created subscription.
| Field | Type | Label | Description |
| subscription_id | int32 | required |
|
Contains performance profile data.
| Field | Type | Label | Description |
| total_calls | int32 | optional |
|
| total_time | double | optional |
|
| functions | PerformanceProfileFunction | repeated |
|
Schedule information for a job.
| Field | Type | Label | Description |
| schedule_id | bytes | optional |
|
| created_at | string | optional |
|
| updated_at | string | optional |
|
| enabled | bool | optional |
|
| time_unit | ScheduleTimeUnit | optional |
|
| num_units | int32 | optional |
|
| timing | ScheduleTiming | optional |
|
| schedule_name | string | optional |
|
| job_name | string | optional |
|
| seeds | string | repeated |
|
| policy_id | bytes | optional |
|
| tags | string | repeated |
|
| job_count | int32 | optional |
|
A list of job schedules.
This seemingly stupid message is necessary so that a list of job schedules can be used as the body of a "oneof".
| Field | Type | Label | Description |
| schedules | Schedule | repeated |
|
A wrapper for all server messages that contains either a response to a command or a subscription event.
| Field | Type | Label | Description |
| event | Event | optional |
|
| response | Response | optional |
|
Sent when the server ends a subscription.
| Field | Type | Label | Description |
| reason | SubscriptionClosed.Reason | required |
|
| message | string | optional |
|
An item sent when syncing a crawl job. One event is sent for each crawl response.
| Field | Type | Label | Description |
| item | CrawlResponse | required |
|
| token | bytes | required |
|
A subtree of Trio tasks.
| Field | Type | Label | Description |
| name | string | optional |
|
| subtasks | TaskTree | repeated |
|
| Name | Number | Description |
| ALPHANUMERIC | 1 | |
| NUMBERS_ONLY | 2 | |
| ALPHA_ONLY | 3 |
The various run states a job may have.
| Name | Number | Description |
| CANCELLED | 1 | |
| COMPLETED | 2 | |
| PAUSED | 3 | |
| PENDING | 4 | |
| RUNNING | 5 | |
| DELETED | 6 | This isn't really a valid run state. It indicates that job no longer exists. |
Specifies how a regex pattern should be used.
| Name | Number | Description |
| MATCHES | 1 | |
| DOES_NOT_MATCH | 2 |
| Name | Number | Description |
| OBEY | 1 | Obey robots.txt rules. |
| INVERT | 2 | Do the opposite of robots.txt rules. |
| IGNORE | 3 | Ignore robots.txt. |
| Name | Number | Description |
| ADD | 1 | Add `amount` to parent cost. |
| MULTIPLY | 2 | Multiply parent cost by `amount`. |
Define time units that may be used for scheduling a job.
| Name | Number | Description |
| MINUTES | 1 | |
| HOURS | 2 | |
| DAYS | 3 | |
| WEEKS | 4 | |
| MONTHS | 5 | |
| YEARS | 6 |
Define when a job should be scheduled.
| Name | Number | Description |
| AFTER_PREVIOUS_JOB_FINISHED | 1 | Schedule a job X units of time after the previous job completes. |
| REGULAR_INTERVAL | 2 | Schedule a job every X units of time; if the previous job is still running, end it. |
| Name | Number | Description |
| COMPLETE | 1 | |
| ERROR | 2 |
| .proto Type | Notes | C++ Type | Java Type | Python Type |
| double | double | double | float | |
| float | float | float | float | |
| int32 | Uses variable-length encoding. Inefficient for encoding negative numbers – if your field is likely to have negative values, use sint32 instead. | int32 | int | int |
| int64 | Uses variable-length encoding. Inefficient for encoding negative numbers – if your field is likely to have negative values, use sint64 instead. | int64 | long | int/long |
| uint32 | Uses variable-length encoding. | uint32 | int | int/long |
| uint64 | Uses variable-length encoding. | uint64 | long | int/long |
| sint32 | Uses variable-length encoding. Signed int value. These more efficiently encode negative numbers than regular int32s. | int32 | int | int |
| sint64 | Uses variable-length encoding. Signed int value. These more efficiently encode negative numbers than regular int64s. | int64 | long | int/long |
| fixed32 | Always four bytes. More efficient than uint32 if values are often greater than 2^28. | uint32 | int | int |
| fixed64 | Always eight bytes. More efficient than uint64 if values are often greater than 2^56. | uint64 | long | int/long |
| sfixed32 | Always four bytes. | int32 | int | int |
| sfixed64 | Always eight bytes. | int64 | long | int/long |
| bool | bool | boolean | boolean | |
| string | A string must always contain UTF-8 encoded or 7-bit ASCII text. | string | String | str/unicode |
| bytes | May contain any arbitrary sequence of bytes. | string | ByteString | str |