Iterators¶
Iterators allow you to traverse over collections of your resources in an efficient and easy way. Currently there are two Iterators provided by the SDK:
- ResourceIterator. The standard iterator class that implements SPL’s standard Iterator, ArrayAccess and Countable interfaces. In short, this allows you to traverse this object (using foreach), count its internal elements like an array (using count or sizeof), and access its internal elements like an array (using $iterator[1]).
- PaginatedIterator. This is a child of ResourceIterator, and as such inherits all of its functionality. The difference however is that when it reaches the end of the current collection, it attempts to construct a URL to access the API based on predictive paginated collection templates.
Common behaviour¶
$iterator = $computeService->flavorList();
There are two ways to traverse an iterator. The first is the longer, more traditional way:
while ($iterator->valid()) {
$flavor = $iterator->current();
// do stuff..
echo $flavor->id;
$iterator->next();
}
There is also a shorter and more intuitive version:
foreach ($iterator as $flavor) {
// do stuff...
echo $flavor->id;
}
Because the iterator implements PHP’s native Iterator interface, it can inherit all the native functionality of traversible data structures with foreach.
Very important note¶
Until now, users have been expected to do this:
while ($flavor = $iterator->next()) {
// ...
}
which is incorrect. The single responsibility of next is to move the internal pointer forward. It is the job of current to retrieve the current element.
For your convenience, these two Iterator classes are fully backward compatible: they exhibit all the functionality you’d expect from a correctly implemented iterator, but they also allow previous behaviour.
Using paginated collections¶
For large collections, such as retrieving DataObjects from CloudFiles/Swift, you need to use pagination. Each resource will have a different limit per page; so once that page is traversed, there needs to be another API call to retrieve to next page’s resources.
There are two key concepts:
- limit is the amount of resources returned per page
- marker is the way you define a starting point. It is some form of identifier that allows the collection to begin from a specific resource
Resource classes¶
When the iterator returns a current element in the internal list, it populates the relevant resource class with all the data returned to the API. In most cases, a stdClass object will become an instance of OpenCloud\Common\PersistentObject.
In order for this instantiation to happen, the resourceClass option must correspond to some method in the parent class that creates the resource. For example, if we specify ‘ScalingPolicy’ as the resourceClass, the parent object (in this case OpenCloud\Autoscale\Group, needs to have some method will allows the iterator to instantiate the child resource class. These are all valid:
- Group::scalingGroup($data);
- Group::getScalingGroup($data);
- Group::resource('ScalingGroup', $data);
where $data is the standard object. This list runs in order of precedence.
Setting up a PaginatedIterator¶
use OpenCloud\Common\Collection\PaginatedIterator;
$service = $client->computeService();
$flavors = PaginatedIterator::factory($service, array(
'resourceClass' => 'Flavor',
'baseUrl' => $service->getUrl('flavors')
'limit.total' => 350,
'limit.page' => 100,
'key.collection' => 'flavors'
));
foreach ($flavors as $flavor) {
echo $flavor->getId();
}
As you can see, there are a lot of configuration parameters to pass in - and getting it right can be quite fiddly, involving a lot of API research. For this reason, using the convenience methods like flavorList is recommended because it hides the complexity.
PaginatedIterator options¶
There are certain configuration options that the paginated iterator needs to work. These are:
| Name | Description | Type | Required | Default |
|---|---|---|---|---|
| resourceClass | The resource class that is instantiated when the current element is retrieved. This is relative to the parent/service which called the iterator. | string | Yes | |
| baseUrl | The base URL that is used for making new calls to the API for new pages | Guzzle\Http\Url | Yes | |
| limit.total | The total amount of resources you want to traverse in your collection. The iterator will stop as this limit is reached, regardless if there are more items in the list | int | No | 10000 |
| limit.page | The amount of resources each page contains | int | No | 100 |
| key.links | Often, API responses will contain “links” that allow easy access to the next page of a resource collection. This option specifies what that JSON element is called (its key). For example, for Rackspace Compute images it is images_links. | string | No | links |
| key.collection | The top-level key for the array of resources. For example, servers are returned with this data structure: {"servers": [...]}. The key.collection value in this case would be servers. | string | No | null |
| key.collectionElement | Rarely used. But it indicates the key name for each nested resource element. KeyPairs, for example, are listed like this: {"keypairs": [ {"keypair": {...}} ] }. So in this case the collectionElement key would be keypair. | string | No | null |
| key.marker | The value used as the marker. It needs to represent a valid property in the JSON resource objects. Often it is id or name. | string | No | name |
| request.method | The HTTP method used when making API calls for new pages | string | No | GET |
| request.headers | The HTTP headers to send when making API calls for new pages | array | No | array() |
| request.body | The HTTP entity body to send when making API calls for new pages | Guzzle\Http\EntityBody | No | null |
| request.curlOptions | Additional cURL options to use when making API calls for new pages | array | No | array() |


{% block head %} {% endblock %}
This is an example server built for the Django framework. It only authenticates one OpenID, which is also served by this application. The OpenID it serves is
{{ local_id }}


Learn How to Make a Website
Learn the essentials of web development and build your own website.
Welcome to Tutorial Republic
At tutorialrepublic.com you will learn the essentials of web development technologies along with real life practice examples, so that you can create your own website. Here you'll find:
Step by Step Tutorial
The tutorial section encloses an extensive collection of tutorials and examples that you can try and test yourself using online HTML editor. You will also find large numbers of demonstrations, tips and techniques covering everything you need to create web pages.
If you're a beginner, start learning from here »
Useful References
The references section outlines all the standard HTML tags and CSS properties along with other useful references such as color names and values, symbols and character entities, web safe fonts, language codes, HTTP messages and much more.
Check out the complete web references »
Interactive Tools
Practice while learning is the best way to learn. At Tutorial Republic you will find number of interactive tools like Code Lab, Color Picker, URL Encoder, Twitter Bootstrap Button Generator and many other tools that you can play with to extend your learning.
Check out the available tools »


Mean income of employed Columbia undergraduates
post-enrollment
However, over time, the mean income
for the class of 2009 is lower than
that of classes that did not graduate
during the Great Recession.
Student incomes six years
after first enrolling at Columbia are
similar across classes.
Mean income of $90K
$60K
$30K
8 years after enrolling
6 years after enrolling
10 years after enrolling
Class of 2009
Class of 2011
Class of 2007
Class of 2013
Source: College Scorecard
Graphic by Eve Washington
Mean income of employed Columbia
undergraduates post-enrollment
Over time the mean income for the class of 2009 is lower than that of classes that did not graduate during the Great Recession.
Mean income of 90K
60K
30K
6
8
10
Number of years after enrolling
Class of 2007
Class of 2009
Class of 2011
Class of 2013
Source: College Scorecard
Graphic by Eve Washington


Get Payment Methods for Offline Deposit
This endpoint allows retrieval of payment methods that should be used with offline deposit (version 2) transactions.
This is a required parameter in the said deposit transaction endpoint and effects the generation of UDA
| Name |
Description |
| Status |
Active |
| Enpoint URI |
api/Common/GetPaymentMethod |
| Method |
GET |
| URI Parameters |
None |
| Body Parameters |
None |
| Request Format |
JSON |
| Response Format |
JSON |
| Name |
Type |
Description |
Sample |
| PaymentMethodCode |
string |
Code assigned to the payment method |
WLKN |
| PaymentMethodName |
string |
Name assigned to the payment method |
Walk-in |
| Code |
Description |
Resolution |
| 200 |
Success |
None |
| 500 |
Internal Server Error |
Verify that you are using the correct Client Key and Secret Key |
| 401 |
Unauthorized |
Check if you're HTTP request header is passed correctly, could be:
- Missing Client Key
- Missing Secret Key
|
| 404 |
Not found |
Contact Customer/Tech Support |


Flakesnow Windows version includes extra features like notes, colorpicker, alarm and timer. They are really useful everyday.
Check weather quickly anywhere you want.
Flakesnow is easy to configure to your personal settings. Easily change location and


http://www.susangranger.com/
Susan Granger's review of "ALL THE PRETTY HORSES" (Miramax)
As muddy and meandering as the Rio Grande, this 1940's Western is the soggy saga of two buddies, Matt Damon and Henry Thomas (the "E.T." kid, now grown up), who ride across the border from Texas to Mexico to be real cowboys. Faithfully adapted by Ted Tally from Cormac McCarthy's fascinating novel, the concept is never fully realized by director Billy Bob Thornton. Instead, the pace is confusing and uneven, nuances that define the characters are under-developed, even the visual style is inconsistent. As the episodic story unfolds, Damon and Thomas are joined on the trail by a cocky kid, Lucas Black ("Sling Blade") who is obviously riding a stolen horse and carrying a stolen gun. They suspect he's going to be trouble - and he is. Then there's the seduction of Damon by Penelope Cruz, the lusty daughter of the aristocratic Mexican, Ruben Blades, who owns the sprawling horse ranch where they've secured jobs. Despite a nocturnal swim under the stars, director Thornton even manages to make their love scenes dull; at one point, they're stupidly commenting about having something up their noses. Miriam Colon scores as Cruz's aunt who's rightfully suspicious about Damon, this gringo who winds up in a Mexican penitentiary, albeit on false charges. Then there's what seems like an awkwardly added epilogue with Damon telling his tale of woe to a sympathetic West Texas judge, played by Bruce Dern. On the Granger Movie Gauge of 1 to 10, "All the Pretty Horses" is ponderous, pretentious 3. Basically, none of the characters - except Miriam Colon's - exude passion or even interest. The actors seem to be going through the motions - and the audience senses it on an conscious or unconscious level, refusing to make an emotional commitment to the tale.
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


Welcome to BurgerHeaven Online
Select burger
This is where you execute burger selection
{{ burger.name }}
- {{ burger.kcal }}kCal
- {{burger.gluten}}
- {{burger.lactose}} Add to cart
Customer information
This is where you provide necessary information
Delivery Information
Click where to deliver on the map!
Open dispatcher in new window.
T


HyperText Markup Language (HTML)
HTML is made up of the following:
Text Content - what you see
Markup - what it looks like
References - to other documents, like images and videos
Links to other pages (hyperlinks)
Markup (tags, atrributes, etc.)
- Markups are made of tags
ex: tag name+contents+close tag name
ex tags: Bold (b /b), italics (em /em), anchor (a href="URL"> text /a>), image (img src="url" alt="text">), break (br (void)), paragraph (p /p>)
- Inline vs. Block
Inline are tags that are created within the same line
Block tags are tags that create an invisible box (boxes can be assigned heights and widths)
HTML Document
DocType
HTML (surrounds the whole doc)
Head (metadata, javascript file references, CSS file references)
Body (contents of the document)


| DOSE: |
3 hits |
smoked |
Cannabis |
(plant material) |
The other day, I went to an amusement park with 3 of my friends. When we returned, we decided it would be a good idea to go swimming at night at my friend Lukas's pond. Lukas is big on smoking pot. I had tried it two other times before, once over a year earlier and the other time about 2 weeks prior to that night. The first time I smoked, I took about 11 'hits' from a bowl and while packing another bowl I fell completely into a dream and started panicking, not knowing where I was. The last time I smoked though, I had not gotten high at all and I was dissapointed so I hoped this night would be better.
When we got to his house, we sat down in the basement, while Lukas and his friend Matthew played ping pong and the other girl Jessica and I watched. 5 or so minutes in, Matthew and Lukas decided to go leave for 10 or so minutes to go buy an ounce or so of weed. They gathered up 35 dollars and sent us to bring down water, a bubbler, and towels/bathing suits to the pond. About then our friend Mark arrived and waited while Jessica and I changed. Then we walked in the dark to the pond. We were having a bit of trouble walking through the brush in the dark, and Mark rescued us with a large flood light/flashlight and we went to go sit by the pond and wait.
Soon Matthew and Lukas arrived, and pulled out the weed while Mark felt it and estimated that the price probably should have been about 10 dollars cheaper. Then they packed the bubbler and started passing it around. Jessica decided not to smoke, but I did. I was the last in the circle of four that were smoking, and I managed one hit before the weed was kicked during the second time passing the bubbler around. They decided then to smoke a joint, and we sat there talking while Mark rolled the joint.
Slowly I began to stare off into space as they talked, and I began to catch snippets of the conversation they were having. Suddenly I realized that I had just said Jessica's name, but had no clue what I was talking about. I felt like I was dreaming, and started laughing uncontrollably. 'Jessica, its like I'm dreaming!' All the boys looked at me and started laughing. 'Dude, you're stoned.' Mark told me. 'After one hit??' I couldn't believe that I had gotten stoned after only one hit, but I could not pay attention long enough to keep wondering about it. I noticed that my tongue felt odd and I kept opening and closing my mouth. I decided finally that I had cottonmouth, and announced loudly one word, 'Cottonmouth!' then went back into my thinking. After what seemed like forever, we started smoking the joint. After it being passed to me twice, I opted to not smoke anymore seeing that I was already too stoned to function.
After the joint was done, Jessica and Mark got into kayaks and paddled out to a floating dock in the middle of the pond. I waded into the water, but refused to swim out to the dock because I seemed to be afraid to be able to touch the bottom. For what seemed like a long time, I stood ankle-deep in the water, stepping forward then backward again, trying to decide whether to go back or to swim into the water. When I realized what I was doing, I started to laugh at myself. Somehow, I finally swam out to the dock and sat with Jessica.
So that we could see, the boys on shore turned on the flood light and pointed it towards us. The light to me looked like a beautiful sunset, a world of black with one sole light and the stretch of the light casting across the water. I told Jessica and Mark, who had suddenly gotten there, that it was just beautiful, gorgeous in fact.  As we sat, Jessica was shivering against me, freezing cold. I noticed that I was cold too, but I could not actually feel it and I could not tell if I was shivering or not. Time passed in a series of getting lost in my thoughts, then coming back, saying something, then becoming embarassed as everyone looked at me funny.
The combination of darkness and the one light confused me and allowed me to have minor visual hallucinations, like seeing my friends that weren't really there, or actually having dreams that I could see while my eyes were open. At one point, I was awoken from my daze of dreams to my friends acting worried and scared because of some noise that was being made in the woods. To me, it sounded like an owl but to them they thought it was a cayote or something. Lukas was the one appointed to swim back to shore and turn off the light so that we could go skinny dipping, and he seemed very afraid. At one point the owl/cayote sounded again and he swept the light across the shore, and suddenly I saw a cartoon lion sitting there. When the light left that spot, the lion dissolved into pink.  I promptly realized that what I had seen wasn't really seeing a lion and was swept back into my thoughts.
Some time later, while I was being driven home with Jessica and our driver Jen, I started watching the road and feeling like I was on a roller coaster. Every hill we went on, I shot up my arms, yelling 'Wee! It's just like the coasters we went on today!' I am not sure whether or not we were actually going fast, but I am still shocked at my reaction because usually I do not feel as 'tossed around' in normal driving settings as I did then. When I was finally dropped off home, I discovered that I had the munchies and devoured chocolate chips, trail mix, and grapefruit, then went to bed still stoned. My dreams were fitful and different than usual, and I woke up wondering whether I was still stoned or not.
What has not been explained in these series of events was how my reaction was different to those of the other kids with me. Everyone else seemed calm, and their remarks at least slightly intelligent, they were able to hold conversations. For me, I experienced constant confusion, and mild visual and auditory hallucinations. This was after only 3 hits. So far both my smoking experiences have left me as the 'event of the night', with everyone talking about my actions and remarks. In the end, I am completely embarassed by my actions and would prefer to smoke alone and be left to my abstract thoughts.
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.


[gecode-users] Analysing search performance
Christian Schulte
schulte at imit.kth.se
Fri Mar 3 13:12:53 CET 2006
Always use recomputation: the default settings for Gecode's search engine
sets the copying distance (c_d) to 8 and the adaptive distance (a_d) to 2!
Recomputation is done in a rather smart way, so it will not hurt big
perfomancewise.
As itc omes ICL_VAL for distinct, it does the obvious: wait until a variable
ceomes assigned and then remove that value from all other variables. In
problems where one has little propagation anyway, this can work well.
Christian
--
Christian Schulte, http://www.imit.kth.se/~schulte/
-----Original Message-----
From: users-bounces at gecode.org [mailto:users-bounces at gecode.org] On Behalf
Of Lars Otten
Sent: Friday, March 03, 2006 1:57 PM
To: users at gecode.org
Subject: Re: [gecode-users] Analysing search performance
On 03/03/06 01:51, Lars Otten wrote:
> The biggest instance I'm currently testing is eating about 1 GB of
> memory when run, so on my machine it is an issue, yes. ;) I am not
> using recomputation at the moment (for direct comparison with my
> randomized search algorithm, which don't use recomputation either),
> but as I found that mostly increases memory consumption anyway...
Hm, actually it does not seem to be quite that simple. Memory consumption
for dfs-reco always seems to be lower, but wrt. running time things
sometimes get better, sometimes worse (compared to dfs-copy).
Is there any rule of thumb when to apply dfs-reco instead of dfs-copy?
> Just tonight, however, I have made some progress by toying with the
> ICL for the distinct propagators that are posted. Especially in
> cooperation with some of the random stuff I implemented, a solution
> seems to be found rather quickly for most instances -- I'm quite happy
> about that at the moment! :))
Ok, so I think I understood the conceptual difference between ICL_DOM and
ICL_BND -- in consequence ICL_BND is 'less accurate' but potentially
propagates faster. But where does ICL_VAL fit into that? I am aware that
these levels are only meant to be guidelines for the propagators, still it
would be interesting to know...
Regards,
/Lars
_______________________________________________
Gecode users mailing list
users at gecode.org https://www.gecode.org/mailman/listinfo/gecode-users
More information about the gecode-users
mailing list


Two killed, some wounded in Israeli attack on Damascus: Syrian state media
Cairo (Reuters) - Two civilians were killed and some wounded in an Israeli attack on the Syrian capital of Damascus, state media said on Wednesday.
Earlier, Israeli military spokesman Avichay Adraee said on Twitter that Israel had attacked Iranian and Syrian military targets in Syria as retaliation for rockets fired toward Israel the day before.
Syria’s air defenses were able to destroy most of the missiles fired by Israeli jets over Damascus before they reached their targets, Syria’s state news agency SANA said, quoting a military source.


Describes the Spot instance requests that belong to your account. Spot instances are instances that Amazon EC2 launches when the bid price that you specify exceeds the current Spot price. Amazon EC2 periodically sets the Spot price based on available Spot instance capacity and current Spot instance requests. For more information, see Spot Instance Requests in the Amazon Elastic Compute Cloud User Guide .
You can use describe-spot-instance-requests to find a running Spot instance by examining the response. If the status of the Spot instance is fulfilled , the instance ID appears in the response and contains the identifier of the instance. Alternatively, you can use describe-instances with a filter to look for instances where the instance lifecycle is spot .
Spot instance requests are deleted 4 hours after they are canceled and their instances are terminated.
See also: AWS API Documentation
describe-spot-instance-requests
[--dry-run | --no-dry-run]
[--spot-instance-request-ids <value>]
[--filters <value>]
[--cli-input-json <value>]
[--generate-cli-skeleton <value>]
--dry-run | --no-dry-run (boolean)
Checks whether you have the required permissions for the action, without actually making the request, and provides an error response. If you have the required permissions, the error response is DryRunOperation . Otherwise, it is UnauthorizedOperation .
--spot-instance-request-ids (list)
One or more Spot instance request IDs.
Syntax:
"string" "string" ...
One or more filters.
- availability-zone-group - The Availability Zone group.
- create-time - The time stamp when the Spot instance request was created.
- fault-code - The fault code related to the request.
- fault-message - The fault message related to the request.
- instance-id - The ID of the instance that fulfilled the request.
- launch-group - The Spot instance launch group.
- launch.block-device-mapping.delete-on-termination - Indicates whether the Amazon EBS volume is deleted on instance termination.
- launch.block-device-mapping.device-name - The device name for the Amazon EBS volume (for example, /dev/sdh ).
- launch.block-device-mapping.snapshot-id - The ID of the snapshot used for the Amazon EBS volume.
- launch.block-device-mapping.volume-size - The size of the Amazon EBS volume, in GiB.
- launch.block-device-mapping.volume-type - The type of the Amazon EBS volume: gp2 for General Purpose SSD, io1 for Provisioned IOPS SSD, st1 for Throughput Optimized HDD, sc1 for Cold HDD, or standard for Magnetic.
- launch.group-id - The security group for the instance.
- launch.image-id - The ID of the AMI.
- launch.instance-type - The type of instance (for example, m3.medium ).
- launch.kernel-id - The kernel ID.
- launch.key-name - The name of the key pair the instance launched with.
- launch.monitoring-enabled - Whether monitoring is enabled for the Spot instance.
- launch.ramdisk-id - The RAM disk ID.
- network-interface.network-interface-id - The ID of the network interface.
- network-interface.device-index - The index of the device for the network interface attachment on the instance.
- network-interface.subnet-id - The ID of the subnet for the instance.
- network-interface.description - A description of the network interface.
- network-interface.private-ip-address - The primary private IP address of the network interface.
- network-interface.delete-on-termination - Indicates whether the network interface is deleted when the instance is terminated.
- network-interface.group-id - The ID of the security group associated with the network interface.
- network-interface.group-name - The name of the security group associated with the network interface.
- network-interface.addresses.primary - Indicates whether the IP address is the primary private IP address.
- product-description - The product description associated with the instance (Linux/UNIX | Windows ).
- spot-instance-request-id - The Spot instance request ID.
- spot-price - The maximum hourly price for any Spot instance launched to fulfill the request.
- state - The state of the Spot instance request (open | active | closed | cancelled | failed ). Spot bid status information can help you track your Amazon EC2 Spot instance requests. For more information, see Spot Bid Status in the Amazon Elastic Compute Cloud User Guide.
- status-code - The short code describing the most recent evaluation of your Spot instance request.
- status-message - The message explaining the status of the Spot instance request.
- tag :key =*value* - The key/value combination of a tag assigned to the resource. Specify the key of the tag in the filter name and the value of the tag in the filter value. For example, for the tag Purpose=X, specify tag:Purpose for the filter name and X for the filter value.
- tag-key - The key of a tag assigned to the resource. This filter is independent of the tag-value filter. For example, if you use both the filter "tag-key=Purpose" and the filter "tag-value=X", you get any resources assigned both the tag key Purpose (regardless of what the tag's value is), and the tag value X (regardless of what the tag's key is). If you want to list only resources where Purpose is X, see the tag :key =*value* filter.
- tag-value - The value of a tag assigned to the resource. This filter is independent of the tag-key filter.
- type - The type of Spot instance request (one-time | persistent ).
- launched-availability-zone - The Availability Zone in which the bid is launched.
- valid-from - The start date of the request.
- valid-until - The end date of the request.
Shorthand Syntax:
Name=string,Values=string,string ...
JSON Syntax:
[
{
"Name": "string",
"Values": ["string", ...]
}
...
]
--cli-input-json (string) Performs service operation based on the JSON string provided. The JSON string follows the format provided by --generate-cli-skeleton. If other arguments are provided on the command line, the CLI values will override the JSON-provided values.
--generate-cli-skeleton (string) Prints a JSON skeleton to standard output without sending an API request. If provided with no value or the value input, prints a sample input JSON that can be used as an argument for --cli-input-json. If provided with the value output, it validates the command inputs and returns a sample output JSON for that command.
To describe Spot Instance requests
This example describes all of your Spot Instance requests.
Command:
aws ec2 describe-spot-instance-requests
Output:
{
"SpotInstanceRequests": [
{
"Status": {
"UpdateTime": "2014-04-30T18:16:21.000Z",
"Code": "fulfilled",
"Message": "Your Spot request is fulfilled."
},
"ProductDescription": "Linux/UNIX",
"InstanceId": "i-1234567890abcdef0",
"SpotInstanceRequestId": "sir-08b93456",
"State": "active",
"LaunchedAvailabilityZone": "us-west-1b",
"LaunchSpecification": {
"ImageId": "ami-7aba833f",
"KeyName": "May14Key",
"BlockDeviceMappings": [
{
"DeviceName": "/dev/sda1",
"Ebs": {
"DeleteOnTermination": true,
"VolumeType": "standard",
"VolumeSize": 8
}
}
],
"EbsOptimized": false,
"SecurityGroups": [
{
"GroupName": "launch-wizard-1",
"GroupId": "sg-e38f24a7"
}
],
"InstanceType": "m1.small"
},
"Type": "one-time",
"CreateTime": "2014-04-30T18:14:55.000Z",
"SpotPrice": "0.010000"
},
{
"Status": {
"UpdateTime": "2014-04-30T18:16:21.000Z",
"Code": "fulfilled",
"Message": "Your Spot request is fulfilled."
},
"ProductDescription": "Linux/UNIX",
"InstanceId": "i-1234567890abcdef1",
"SpotInstanceRequestId": "sir-285b1e56",
"State": "active",
"LaunchedAvailabilityZone": "us-west-1b",
"LaunchSpecification": {
"ImageId": "ami-7aba833f",
"KeyName": "May14Key",
"BlockDeviceMappings": [
{
"DeviceName": "/dev/sda1",
"Ebs": {
"DeleteOnTermination": true,
"VolumeType": "standard",
"VolumeSize": 8
}
}
],
"EbsOptimized": false,
"SecurityGroups": [
{
"GroupName": "launch-wizard-1",
"GroupId": "sg-e38f24a7"
}
],
"InstanceType": "m1.small"
},
"Type": "one-time",
"CreateTime": "2014-04-30T18:14:55.000Z",
"SpotPrice": "0.010000"
}
]
}
SpotInstanceRequests -> (list)
One or more Spot instance requests.
(structure)
Describes a Spot instance request.
SpotInstanceRequestId -> (string)
The ID of the Spot instance request.SpotPrice -> (string)
The maximum hourly price (bid) for the Spot instance launched to fulfill the request.Type -> (string)
The Spot instance request type.State -> (string)
The state of the Spot instance request. Spot bid status information can help you track your Spot instance requests. For more information, see Spot Bid Status in the Amazon Elastic Compute Cloud User Guide .Fault -> (structure)
The fault codes for the Spot instance request, if any.
Code -> (string)
The reason code for the Spot instance state change.Message -> (string)
The message for the Spot instance state change.Status -> (structure)
The status code and status message describing the Spot instance request.
Code -> (string)
The status code. For a list of status codes, see Spot Bid Status Codes in the Amazon Elastic Compute Cloud User Guide .UpdateTime -> (timestamp)
The date and time of the most recent status update, in UTC format (for example, YYYY -MM -DD T*HH* :MM :SS Z).Message -> (string)
The description for the status code.ValidFrom -> (timestamp)
The start date of the request, in UTC format (for example, YYYY -MM -DD T*HH* :MM :SS Z). The request becomes active at this date and time.ValidUntil -> (timestamp)
The end date of the request, in UTC format (for example, YYYY -MM -DD T*HH* :MM :SS Z). If this is a one-time request, it remains active until all instances launch, the request is canceled, or this date is reached. If the request is persistent, it remains active until it is canceled or this date is reached.LaunchGroup -> (string)
The instance launch group. Launch groups are Spot instances that launch together and terminate together.AvailabilityZoneGroup -> (string)
The Availability Zone group. If you specify the same Availability Zone group for all Spot instance requests, all Spot instances are launched in the same Availability Zone.LaunchSpecification -> (structure)
Additional information for launching instances.
ImageId -> (string)
The ID of the AMI.KeyName -> (string)
The name of the key pair.SecurityGroups -> (list)
One or more security groups. When requesting instances in a VPC, you must specify the IDs of the security groups. When requesting instances in EC2-Classic, you can specify the names or the IDs of the security groups.
(structure)
Describes a security group.
GroupName -> (string)
The name of the security group.GroupId -> (string)
The ID of the security group.UserData -> (string)
The user data to make available to the instances. If you are using an AWS SDK or command line tool, Base64-encoding is performed for you, and you can load the text from a file. Otherwise, you must provide Base64-encoded text.AddressingType -> (string)
Deprecated.InstanceType -> (string)
The instance type.Placement -> (structure)
The placement information for the instance.
AvailabilityZone -> (string)
The Availability Zone.
[Spot fleet only] To specify multiple Availability Zones, separate them using commas; for example, "us-west-2a, us-west-2b".
GroupName -> (string)
The name of the placement group (for cluster instances).Tenancy -> (string)
The tenancy of the instance (if the instance is running in a VPC). An instance with a tenancy of dedicated runs on single-tenant hardware. The host tenancy is not supported for Spot instances.KernelId -> (string)
The ID of the kernel.RamdiskId -> (string)
The ID of the RAM disk.BlockDeviceMappings -> (list)
One or more block device mapping entries.
Although you can specify encrypted EBS volumes in this block device mapping for your Spot Instances, these volumes are not encrypted.
(structure)
Describes a block device mapping.
VirtualName -> (string)
The virtual device name (ephemeral N). Instance store volumes are numbered starting from 0. An instance type with 2 available instance store volumes can specify mappings for ephemeral0 and ephemeral1 .The number of available instance store volumes depends on the instance type. After you connect to the instance, you must mount the volume.
Constraints: For M3 instances, you must specify instance store volumes in the block device mapping for the instance. When you launch an M3 instance, we ignore any instance store volumes specified in the block device mapping for the AMI.
DeviceName -> (string)
The device name exposed to the instance (for example, /dev/sdh or xvdh ).Ebs -> (structure)
Parameters used to automatically set up EBS volumes when the instance is launched.
SnapshotId -> (string)
The ID of the snapshot.VolumeSize -> (integer)
The size of the volume, in GiB.
Constraints: 1-16384 for General Purpose SSD (gp2 ), 4-16384 for Provisioned IOPS SSD (io1 ), 500-16384 for Throughput Optimized HDD (st1 ), 500-16384 for Cold HDD (sc1 ), and 1-1024 for Magnetic (standard ) volumes. If you specify a snapshot, the volume size must be equal to or larger than the snapshot size.
Default: If you're creating the volume from a snapshot and don't specify a volume size, the default is the snapshot size.
DeleteOnTermination -> (boolean)
Indicates whether the EBS volume is deleted on instance termination.VolumeType -> (string)
The volume type: gp2 , io1 , st1 , sc1 , or standard .
Default: standard
Iops -> (integer)
The number of I/O operations per second (IOPS) that the volume supports. For io1 , this represents the number of IOPS that are provisioned for the volume. For gp2 , this represents the baseline performance of the volume and the rate at which the volume accumulates I/O credits for bursting. For more information about General Purpose SSD baseline performance, I/O credits, and bursting, see Amazon EBS Volume Types in the Amazon Elastic Compute Cloud User Guide .
Constraint: Range is 100-20000 IOPS for io1 volumes and 100-10000 IOPS for gp2 volumes.
Condition: This parameter is required for requests to create io1 volumes; it is not used in requests to create gp2 , st1 , sc1 , or standard volumes.
Encrypted -> (boolean)
Indicates whether the EBS volume is encrypted. Encrypted Amazon EBS volumes may only be attached to instances that support Amazon EBS encryption.NoDevice -> (string)
Suppresses the specified device included in the block device mapping of the AMI.SubnetId -> (string)
The ID of the subnet in which to launch the instance.NetworkInterfaces -> (list)
One or more network interfaces. If you specify a network interface, you must specify subnet IDs and security group IDs using the network interface.
(structure)
Describes a network interface.
NetworkInterfaceId -> (string)
The ID of the network interface.DeviceIndex -> (integer)
The index of the device on the instance for the network interface attachment. If you are specifying a network interface in a run-instances request, you must provide the device index.SubnetId -> (string)
The ID of the subnet associated with the network string. Applies only if creating a network interface when launching an instance.Description -> (string)
The description of the network interface. Applies only if creating a network interface when launching an instance.PrivateIpAddress -> (string)
The private IPv4 address of the network interface. Applies only if creating a network interface when launching an instance. You cannot specify this option if you're launching more than one instance in a run-instances request.Groups -> (list)
The IDs of the security groups for the network interface. Applies only if creating a network interface when launching an instance.
(string)
DeleteOnTermination -> (boolean)
If set to true , the interface is deleted when the instance is terminated. You can specify true only if creating a new network interface when launching an instance.PrivateIpAddresses -> (list)
One or more private IPv4 addresses to assign to the network interface. Only one private IPv4 address can be designated as primary. You cannot specify this option if you're launching more than one instance in a run-instances request.
(structure)
Describes a secondary private IPv4 address for a network interface.
PrivateIpAddress -> (string)
The private IPv4 addresses.Primary -> (boolean)
Indicates whether the private IPv4 address is the primary private IPv4 address. Only one IPv4 address can be designated as primary.SecondaryPrivateIpAddressCount -> (integer)
The number of secondary private IPv4 addresses. You can't specify this option and specify more than one private IP address using the private IP addresses option. You cannot specify this option if you're launching more than one instance in a run-instances request.AssociatePublicIpAddress -> (boolean)
Indicates whether to assign a public IPv4 address to an instance you launch in a VPC. The public IP address can only be assigned to a network interface for eth0, and can only be assigned to a new network interface, not an existing one. You cannot specify more than one network interface in the request. If launching into a default subnet, the default value is true .Ipv6Addresses -> (list)
One or more IPv6 addresses to assign to the network interface. You cannot specify this option and the option to assign a number of IPv6 addresses in the same request. You cannot specify this option if you've specified a minimum number of instances to launch.
(structure)
Describes an IPv6 address.
Ipv6Address -> (string)
The IPv6 address.Ipv6AddressCount -> (integer)
A number of IPv6 addresses to assign to the network interface. Amazon EC2 chooses the IPv6 addresses from the range of the subnet. You cannot specify this option and the option to assign specific IPv6 addresses in the same request. You can specify this option if you've specified a minimum number of instances to launch.IamInstanceProfile -> (structure)
The IAM instance profile.
Arn -> (string)
The Amazon Resource Name (ARN) of the instance profile.Name -> (string)
The name of the instance profile.EbsOptimized -> (boolean)
Indicates whether the instance is optimized for EBS I/O. This optimization provides dedicated throughput to Amazon EBS and an optimized configuration stack to provide optimal EBS I/O performance. This optimization isn't available with all instance types. Additional usage charges apply when using an EBS Optimized instance.
Default: false
Monitoring -> (structure)
Describes the monitoring of an instance.
Enabled -> (boolean)
Indicates whether detailed monitoring is enabled. Otherwise, basic monitoring is enabled.InstanceId -> (string)
The instance ID, if an instance has been launched to fulfill the Spot instance request.CreateTime -> (timestamp)
The date and time when the Spot instance request was created, in UTC format (for example, YYYY -MM -DD T*HH* :MM :SS Z).ProductDescription -> (string)
The product description associated with the Spot instance.BlockDurationMinutes -> (integer)
The duration for the Spot instance, in minutes.ActualBlockHourlyPrice -> (string)
If you specified a duration and your Spot instance request was fulfilled, this is the fixed hourly price in effect for the Spot instance while it runs.Tags -> (list)
Any tags assigned to the resource.
(structure)
Describes a tag.
Key -> (string)
The key of the tag.
Constraints: Tag keys are case-sensitive and accept a maximum of 127 Unicode characters. May not begin with aws:
Value -> (string)
The value of the tag.
Constraints: Tag values are case-sensitive and accept a maximum of 255 Unicode characters.
LaunchedAvailabilityZone -> (string)
The Availability Zone in which the bid is launched.


The pioneering years of international athletics
During much of the Georgian era - 1760 to around 1820s - we find slight
evidence of contact between English and overseas runners, just occasional
references like those to the great Levi Whitehead winning the five Queen
Anne's guineas from a field of ten including 'the famous Indian' and 'Long
Joe' failing in an attempt on 10 miles in 58 minutes in 1794 after beating
'the famous Spaniard'.
Around the time of the first gymnastic craze we do begin to glimpse a
growing international dimension to competitive athletics. It is this
development, particularly through English pedestrianism's links with
continental Europe and North America, which we here attempt to illustrate in
the following survey covering the period 1826 to 1878.
1826. John Berry of Lancashire beat the German velocipedist, Maurice Rummel,
over 10 miles on the Uxbridge road from the first milestone near Kensington
Gardens to the sixth beyond Acton and back. Many foreigners attended and for
the first three miles the roadside was packed with spectators, the Germans
backing their man freely though in small amounts. Rummel took an early lead
but Berry caught him at Acton and on the return stretch nearing Notting Hill
bounded, away to win by 30 yards. 'All the spectators whether English or
foreign, admitted a better contested match had never been witnessed'.
Rummell, a very fine active youth - small, but symmetrical person', had
previously won a wager for the Prince de Leon by covering 2½ French leagues
(almost 7 miles) in 36 minutes (on his velocipede?).
1827. At Sunbury Rummel lost to Berry over 5 miles and to James Wantling
over 250 yards. The last defeat is scarcely surprising since Wantling, at
least by reputation, was the top sprinter of the pre-Victorian era. Later
in, the year, principally because of the extreme heat, Rummel failed in his
attempt to run 10 miles in one hour on the Lewes road.
1827. Robert Skipper, long-distance walker, beat 'the celebrated Frenchman'
in Paris. For Skipper, see John Goulstone's monograph John Townsend, the
Sussex Pedestrian (1999), note 1.
1828. George Hall from the Potteries won a hard-fought 350-yard, race by
half a yard against Dufont for 2,000 a-side at St Germains near Paris,
before 'a numerous attendance of the English residents'. Doubtless many of
the latter were connected with the Paris Cricket Club (in 1829 called the
Albion club and an English cricket club) whose membership in 1828 included
'60 persons of the first families in the French capital' who attended in
force its matches on the plains of Monceaux.
1828. The French velocipedist, John Joseph Grandserre, offered to run (ride
a velocipe?) 19 times round the Inner Circle In Regents Park, an estimated
19 miles, in 2 hours. A few months later John Shepherd beat him with
remarkable ease over a 10-mile course around a circle, a 'third of a mile
round, staked out at Lord's'.  Seeing
this, Grandserre put in a terrific burst to go 50 yards ahead. Then Shepherd
passed him with the rapidity of lightning, and at the end of his 10 miles
went to the adjoining house for a nap. Those who had betted on 'the
Frenchman' thereupon claimed he had run one lap short. When told about this,
'out of bed he jumped, ran out of the house, and proceeded round the circle
for the thirty-first time, and before his opponent had completed his
twenty-ninth round' (for further details see John Goulstone's 'John
Shepherd, The Yorkshire Phenomenon', Sports History 9 (1986), pp. 7-9).
1831. Augustus do Berenger (said to be Prussian-born) founded the Stadium at
Chelsea. It was intended to cover foot racing and leaping. Also, 'leaping,
jumping, &c' (a distinction left unexplained) were on the programme of its
projected 'Olympic Festival' in 1832. But so far as one can tell, track and
field never featured at his 'school of athletes' (see John Goulstone's
pamphlet, The Chelsea Stadium or British National Arena, 1831-1843, 1999).
1837. Pedestrian Challenge from France issued by 'Bipedis' to Burn or Fuller
to walk 10 miles at Boulogne for 2,000f - Burn evens, but Fuller 'I expect
to give my man (at present in Paris) two minutes'.
1839. The German Henry Wolfe or Wolff challenged any man in Birmingham at
one mile. He was accepted by, and lost to, William Sheppard, one of the
great milers of the 1840s.
1842. A match staged between a Kentish runner and one from Calais at
Tilmanstone, eight miles from Dover.
1843. Foot racing for the last nine months has been very fashionable in
Paris, and a groom known as Flying Ben 'has often thrown down the gauntlet
to all Paris'. Numerous tradesmen, mostly from Nottingham and Sheffield,
'towns standing high in reputation for pedestrianism', undertook to find a
man from the gas-works to run the groom at 100 yards for 100f in the Bois de
Boulogne. The 'Gasman', trained by a celebrated pedestrian then living in
Paris won before a considerable number of French and English amateurs. 'The
French were highly delighted with the sport, and have promised their support
upon future occasions'. On Christmas Day, Flying Ben lost by 20 yards in the
Bois de Boulogne, over one mile for 200f, to a lad under the superintendence
of 'the Old London Pedestrian'.
1844. The 'sporting landlord', Bob Cowans, arranged a match in which the
Rochechorcott Gas Man, beat 'Bob Logic' for 200f by 6 yards in 150 in the
Bois de Boulogne on 7 January (Sunday, a favourite day for amusements in
France).
1844. The 'perseverance and exertions with the nobility and, gentry in [sic]
behalf of athletic sports' of 'an old London professor', now in Paris,
succeeded in raising a prize of 200f to be run for (distance, one mile) by
persons of all countries, who have resided at least six months within ten
miles of Paris. Prizes were given by a sporting English lord and his
friends, with a 10f sweepstakes, for a mile race in the Bois de Boulogne
watched by several members of the Jockey Club 'and other patrons of athletic
amusements' - won by an English lad in 5 minutes 50 seconds, with a
Frenchman, considered the first runner in France, second and a groom third.
1844. A 2-mile race in the Bois de Boulogne announced for pedestrians
resident at least 6 months in Paris for 100f plus a 20f sweepstakes payable
to Mr Cootes, the second runner to have his money refunded.
1846. English foot races, in the Champs d'Elysees and Bois de Boulogne,
'created a great deal of interest among the French and English residents'.
1847. Paris is rapidly becoming 'a perfect new market in sporting affairs
among the working Englishman, in foot racing, horse racing, cricketing, &c.'
.
1856. George Frost the 'Suffolk Stag' beat Antonio Genaro 'the celebrated
Spanish pedestrian', at the New Surrey Pedestrian Ground, Wandsworth - a
4-hour race which partook somewhat of a national character, the
nimble-footed son of Hispania having been warmly taken by the hand, and
spiritedly patronised, by some of his fellow-countrymen residing in the
metropolis. Genaro arrived in a cloak and a blue cap, embroidered Genaro
Andarin Espanol (Genaro the Spanish Runner) and surmounted by the crown of
Spain. 'The peculiarity of his gait, unusual to an English eye, struck
everyone; he did not lift his feet more than 2 or 3 inches and let them
descend quite flatly upon the ground' in short rapid steps. He gave up after
the 14th mile in 1 hour 38 minutes 2 seconds, with Frost 11 laps ahead. For
full details see Sports Quarterly Magazine 19 (1981), pp. 19-21.
1861. Capt. William Henry Patten Saunders matched against M. Gambiere of
France for 2,500f a-side in 'the Great Running Match for the Championship of
France' near Paris. Gambiere forfeited when he heard of Saunders' trial
time. The Captain was styled the undefeated European Champion, having
contended victoriously for 'the sash' in Russia, Spain, Austria, Prussia and
England. His Russian race was against 'the Tartar Chief', believed
invincible in the eastern Russian Empire. When brought to Moscow, however,
Saunders 'astonished the Muscovites' by winning over 2 miles with ease in 9
minutes 18 seconds. For his career as an athlete, steeplechase jockey,
swimmer, swordsman, big-game hunter, yachtsman, bull-fighter, political
theorist and statistician, poet, novelist and claimed 'master of Coptic
lore' see Sports History 2 (1982), pp. 18-22.
1862. International athletics meeting on Bonn cricket ground held under the
auspices of the English residents. The competitors, mostly students at Bonn
University, came from France, Germany, Russia, Poland, Hungary, Greece and
North and South America as well as from Britain (cf. Sports Quarterly
Magazine 18 (1981), pp. 5-6).
1862. Moorex 'the Italian giant' began a 1,000 miles in 1,000 hours walk at
Warren House, Lindley Moor (information: P. Lovesey).
1862. The Illustrated Sporting News published a portrait of William Birks as
'Champion Pedestrian of France'. He followed an early running career in
Nottinghamshire (with a win over Seward at Trent Bridge in 1847), then lived
in Calais (by 1851), Radford, Nottingham and Oxford before becoming landlord
of the Nottingham Castle, Calais, by 1862.
1877. George Hazael beat the Italian Achille Bargozzi, a native of Forlì and
self-styled champion runner of France and Italy, who claimed to have run 50
miles in 6 hours. 'The International Running Match' over 30 miles for £50
was held at Lillie Bridge with Bargozzi retiring within 50 yards of his 15th
mile, five laps behind Hazael who completed 20 miles - in the then record 1
hour, 57 minutes, 27 seconds - before being declared the winner. It was
actually Hazael who at Islington's Agricultural Hall in 1879, first broke 6
hours for 50 miles. He afterwards ran in America where in Madison Square
Garden in 1882 he also became the first to complete 600 miles in 6 days. In
1885 he installed a running track behind his hotel in Brooklyn.
John Goulstone


Master index
Index for PS_primal_sketch\viz
Dependency Graph for PS_primal_sketch\viz
Generated on Sun 30-Sep-2007 20:39:06 by
m2html
© 2003


Dialogues
What would the city be without the traces of the past? What would we be without them? Everything around us carries memories.
Then and now The tobacco warehouse is located in the modern urban fabric of Xanthi, is not in use and has suffered several major damages, especially on the roof. The greatest extent of the facades and the roof is being restored, while we create a contradictory addition to the northern façade and the roof in order to further emphasize the historical specificity of the building.
Public and Private We choose to create a co-working space, with open spaces for studying, cultural activities and relaxing, and private spaces for startup companies or young people who cannot afford the rent of an individual workspace.
Then and now The tobacco warehouse is located in the modern urban fabric of Xanthi, is not in use and has suffered several major damages, especially on the roof. The greatest extent of the facades and the roof is being restored, while we create a contradictory addition to the northern façade and the roof in order to further emphasize the historical specificity of the building.
Public and Private We choose to create a co-working space, with open spaces for studying, cultural activities and relaxing, and private spaces for startup companies or young people who cannot afford the rent of an individual workspace.
academic year: 2015-2016
team: Georgiadou E., Dalgkali I., Kousoula S., Panagiotopoulou M.


Past Javascript Projects
- Archives page 1
- Chapter 7 - Time Past/Left Calculator
- Chapter 8 - Quick Survey
- Chapter 9 - Form Validation
- Chapter 10 - Your Location
- Chapter 11 - Oops! 404
- Chapter 12 - jQuery Replacement
- Final Project - Tutorial
Time Calculator
Chapter 7: Curious how much time has or will pass? Select a date below to find out.
< previous
next >
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
close ☒
Quick Survey
Chapter 8: Please take a moment to fill out this creative and super original survey! ;)
Form Security
Chapter 9: Further securing the conact form.
Your Location
Chapter 10: Map showing your current location.
Missed Assignment
Chapter 11: Whoopsie, please skip over this one.
jQuery Replacement
Chapter 12: Converted prior Javascript coordinates and error to jQuerry. They are hidden unless activated.