JavaScript is disabled on your browser.
Skip navigation links
Overview
Package
Class
Use
Tree
Deprecated
Index
Help
Prev Letter
Next Letter
Frames
No Frames
All Classes
A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
Q
R
S
T
U
V
W
X
Y
Z
U
underlay(String)
- Method in class com.cloudinary.
Transformation
underlay(AbstractLayerBuilder<?>)
- Method in class com.cloudinary.
Transformation
underlaying()
- Method in class com.cloudinary.
Coordinates
UnknownError
- Exception in
com.cloudinary
UnknownError(String)
- Constructor for exception com.cloudinary.
UnknownError
unsignedDownloadUrlPrefix(String, String, boolean, boolean, Boolean, String, boolean, String)
- Method in class com.cloudinary.
Url
unsignedImageUploadTag(String, String, Map, Map<String, Object>)
- Method in class com.cloudinary.
Uploader
unsignedUpload(Object, String, Map)
- Method in class com.cloudinary.
Uploader
UnsupportedOperationException
- Exception in
com.cloudinary
UnsupportedOperationException(String)
- Constructor for exception com.cloudinary.
UnsupportedOperationException
update(String, Map)
- Method in class com.cloudinary.
Api
update(Map)
- Method in class com.cloudinary.
Configuration
updateTransformation(String, Map, Map)
- Method in class com.cloudinary.
Api
updateUploadMapping(String, Map)
- Method in class com.cloudinary.
Api
updateUploadPreset(String, Map)
- Method in class com.cloudinary.
Api
upload(Object, Map)
- Method in class com.cloudinary.
Uploader
uploader()
- Method in class com.cloudinary.
Cloudinary
uploader
- Variable in class com.cloudinary.strategies.
AbstractUploaderStrategy
Uploader
- Class in
com.cloudinary
Uploader(Cloudinary, AbstractUploaderStrategy)
- Constructor for class com.cloudinary.
Uploader
UploaderStrategy
- Class in
com.cloudinary.codename1
UploaderStrategy()
- Constructor for class com.cloudinary.codename1.
UploaderStrategy
uploadLarge(Object, Map)
- Method in class com.cloudinary.
Uploader
uploadLarge(Object, Map, int)
- Method in class com.cloudinary.
Uploader
uploadLargeRaw(Object, Map)
- Method in class com.cloudinary.
Uploader
uploadLargeRaw(Object, Map, int)
- Method in class com.cloudinary.
Uploader
uploadMapping(String, Map)
- Method in class com.cloudinary.
Api
uploadMappings(Map)
- Method in class com.cloudinary.
Api
uploadPrefix
- Variable in class com.cloudinary.
Configuration
uploadPreset(String, Map)
- Method in class com.cloudinary.
Api
uploadPresets(Map)
- Method in class com.cloudinary.
Api
uploadTagParams(Map)
- Method in class com.cloudinary.
Uploader
url()
- Method in class com.cloudinary.
Cloudinary
Url
- Class in
com.cloudinary
Url(Cloudinary)
- Constructor for class com.cloudinary.
Url
usage(Map)
- Method in class com.cloudinary.
Api
USER_AGENT
- Static variable in class com.cloudinary.
Cloudinary
USER_AGENT
- Static variable in class com.cloudinary.
Configuration
useRootPath
- Variable in class com.cloudinary.
Configuration
useRootPath(boolean)
- Method in class com.cloudinary.
Url
Util
- Class in
com.cloudinary
Util()
- Constructor for class com.cloudinary.
Util
A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
Q
R
S
T
U
V
W
X
Y
Z
Skip navigation links
Overview
Package
Class
Use
Tree
Deprecated
Index
Help
Prev Letter
Next Letter
Frames
No Frames
All Classes


When to Use Cookies and LocalStorage
Problem: I need to persist data.
When to use localstorage:
- I need to persist data for just my client-side code. This will always be stored at domain-global scope.
When to use cookies:
- I need to persist & share data with my server-side code. This can be from client to server or server to server. This can be page, app, or global-mounted scopes.
Local-storage Best Practices:
- A global domain (https://mysite.com) has to share less than 5MB of localStorage on the devices with the lowest quotas. Be a good neighbor.
- LocalStorage doesn’t have its’ own expire system, so embed storage/expire timestamps in the objects your store and set up a mechanism for garbage-collecting it when it is old.
- Use the API correctly. To store things, store objects or strings with
window.localstorage.setItem('myKey','myValue')
orwindow.localstorage.setItem('myKey',myObject)
Cookies best-practices:
- Browser limits on cookies per domain are as low as 4KB. It’s easier than you think to hit this limit when using global cookies for lots of things.
- We need to use these bytes more wisely, especially because they are transmitted as headers on every request per domain.
- Always use the existing cookie methods to get, set, and unset cookies, to avoid obliterating any other mission-critical cookies or writing excess code to solve the same problem
Mount on tightest scope you can.
- Cookies are transmitted on every request that shares its’ domain. If all the cookies are set on the “/” domain, they will be transmitted with EVERY request that browser makes to every app and endpoint also mounted on that same domain.
- If you only need to persist the data on a page, mount the cookie to the page’s scope ("/photos/people"). If you need to persist the data across multiple pages of your app, mount it to your app’s scope ("/photos/"). If you need to persist the data across multiple apps/routes, you can mount the cookie at the domain root “/”
Shortest Expires.
Set expires for as short a time as possible. If possible, use session cookies (expire after tab close or navigation off). This will help the cookie disappear once it is not being used anymore, taking it’s performance cost along with it.
Store only when you really need it.
Default states and most common settings should not set cookies, we should only store the exceptions. If 99% of users have frog=true
, you should only set and check for a cookie when frog=false
, so that only 1% of users incur the performance penalty while the cookie is being used.
Store as few bytes as possible.
- Your cookie names and keys should be short and unique. Save space on character length, but when mounting in the global domain, be sure your cookie name won’t collide with someone else’s.
- You should use a library to condense and unpack the cookies if you have any complex data, so you’re transmitting as few bytes as possible, while not manually handling the formatting each time.
- Do not use json, use form-encoding (a=1;b=0) or querystring (a=1&b=0) format. JSON is extremely wasteful on character length once you have encoded it properly. The other formats use far fewer characters, and are easy to encode/decode and read without the size ballooning.
- When storing true/false values, use 1/0, to save bytes.
- Combine multiple similar settings into one cookie, rather than having a cookie for each key/value pair. This also helps with organization and DRY code. For example: exp: a=0;b=1;


This site uses cookies to provide you with the best user experience. Find out more about our cookie policy here. By clicking "Accept" you consent to use our cookies.
To use our website you must consent to use our cookies.


Sean T. McBeth
Makes things out of a habitual need to remain occupied and entertained.
Current Projects
- Just Write, Dammit! A book writing platform
- SqlSiphon: a database management library for .NET
- Highland Fundraising Solutions: a consultancy for helping non-profits wrangle their data
- Some HTML 5 video fiddling
Writing and Art
- Tumblr blog: essays and photography
- Three Years: an ebook
- Photography and writing on the Galapagos Islands
- Abstract photography with prisms
- MAKE Magazine, Issue 35: Making Pigments
Past Projects
- Brian: a (incomplete) roguelike about a fish
- Small Town: an interactive fiction platform with AI Shakesperean actors
- Mobile-responsive Pong game
- The No-Video Game
- Standing Workstation
- Scratch Live! An HTML 5 synthesizer
- Indie-movie pyrotechnic effects


Masamune_kun_no_Revenge
Masamune Makabe was mercilessly teased for being overweight as child, especially by a girl named Aki Adagaki. Masamune decides to get his sweet revenge by transforming himself into an attractive, intelligent, and athletic young man. After many years honing his new persona, he transfers to Aki's school in hopes of finally getting his long-awaited vengeance.


A demonstration of Hooke's Law. Balls of random location and mass are connected arbitrarily with rubber bands of random strength and minimum lax distance.


Positioning elements is one of the most important features to CSS, but can also be extremely confusing. In fact, I wrote this blog post b/c I was confused about positioning myself. Here I will go through the differences between Absolute, Relative, and Fixed positioning. There's a fourth type called Static, but that is the default position for any element, and is rarely ever used in CSS.
The first type of positioning is Absolute.  The coordinates you type in are based on the screen. So if you type in
Selector {
position: absolute;
top: 0px;
left: 0px;
}
the element will be place in the top left corner of your screen. Absolute positioning can be great and easy, but it also takes elements out from the flow of the page, meaning it's difficult to use with other objects. This is where Relative Positioning comes inRelative Positioning places an object relative to itself and where it fits normally on the page. If you type in the same code as above but use relative instead of absolute, the object won't move at all because you told it to move from its top 0px and from its left 0px.
Fixed Positioning essentially glues an object to the page so when you scroll the object an still be seen. It is great if you want a navagational bar to always be seen, but it can be dangerous because you don't want a fixed object to cover up other objects as you scroll down the page. Each type of position has its own pros and cons and figuring out which position is the best all depends on what type of design you want for your site.
Nick Siefken


{% extends "layout.html" %} {% block page_title %} GOV.UK prototype kit {% endblock %} {% block content %} {% include "includes/phase_banner_beta.html" %} Enter your reset code A password reset code has been sent to<EMAIL_ADDRESS>reset code Reset code {% endblock %}
A password reset code has been sent to pete.kowalczyk@gmail.com.


AWS::Route53::RecordSet AliasTarget
Alias records only: Information about the AWS resource, such as a CloudFront distribution or an Amazon S3 bucket, that you want to route traffic to.
When creating records for a private hosted zone, note the following:
-
Creating geolocation alias and latency alias records in a private hosted zone is allowed but not supported.
-
For information about creating failover records in a private hosted zone, see Configuring Failover in a Private Hosted Zone.
Syntax
To declare this entity in your AWS CloudFormation template, use the following syntax:
JSON
{ "DNSName" :
String
, "EvaluateTargetHealth" :Boolean
, "HostedZoneId" :String
}
YAML
DNSName:
String
EvaluateTargetHealth:Boolean
HostedZoneId:String
Properties
DNSName
-
Alias records only: The value that you specify depends on where you want to route queries:
- Amazon API Gateway custom regional APIs and edge-optimized APIs
-
Specify the applicable domain name for your API. You can get the applicable value using the AWS CLI command get-domain-names:
-
For regional APIs, specify the value of
regionalDomainName
. -
For edge-optimized APIs, specify the value of
distributionDomainName
. This is the name of the associated CloudFront distribution, such asda1b2c3d4e5.cloudfront.net
.
Note The name of the record that you're creating must match a custom domain name for your API, such as
api.example.com
. -
- Amazon Virtual Private Cloud interface VPC endpoint
-
Enter the API endpoint for the interface endpoint, such as
vpce-123456789abcdef01-example-us-east-1a.elasticloadbalancing.us-east-1.vpce.amazonaws.com
. For edge-optimized APIs, this is the domain name for the corresponding CloudFront distribution. You can get the value ofDnsName
using the AWS CLI command describe-vpc-endpoints. - CloudFront distribution
-
Specify the domain name that CloudFront assigned when you created your distribution.
Your CloudFront distribution must include an alternate domain name that matches the name of the record. For example, if the name of the record is acme.example.com, your CloudFront distribution must include acme.example.com as one of the alternate domain names. For more information, see Using Alternate Domain Names (CNAMEs) in the Amazon CloudFront Developer Guide.
You can't create a record in a private hosted zone to route traffic to a CloudFront distribution.
Note For failover alias records, you can't specify a CloudFront distribution for both the primary and secondary records. A distribution must include an alternate domain name that matches the name of the record. However, the primary and secondary records have the same name, and you can't include the same alternate domain name in more than one distribution.
- Elastic Beanstalk environment
-
If the domain name for your Elastic Beanstalk environment includes the region that you deployed the environment in, you can create an alias record that routes traffic to the environment. For example, the domain name
my-environment.us-west-2.elasticbeanstalk.com
is a regionalized domain name.Important For environments that were created before early 2016, the domain name doesn't include the region. To route traffic to these environments, you must create a CNAME record instead of an alias record. Note that you can't create a CNAME record for the root domain name. For example, if your domain name is example.com, you can create a record that routes traffic for acme.example.com to your Elastic Beanstalk environment, but you can't create a record that routes traffic for example.com to your Elastic Beanstalk environment.
For Elastic Beanstalk environments that have regionalized subdomains, specify the
CNAME
attribute for the environment. You can use the following methods to get the value of the CNAME attribute:-
AWS Management Console: For information about how to get the value by using the console, see Using Custom Domains with AWS Elastic Beanstalk in the AWS Elastic Beanstalk Developer Guide.
-
Elastic Beanstalk API: Use the
DescribeEnvironments
action to get the value of theCNAME
attribute. For more information, see DescribeEnvironments in the AWS Elastic Beanstalk API Reference. -
AWS CLI: Use the
describe-environments
command to get the value of theCNAME
attribute. For more information, see describe-environments in the AWS CLI.
-
- ELB load balancer
-
Specify the DNS name that is associated with the load balancer. Get the DNS name by using the AWS Management Console, the ELB API, or the AWS CLI.
-
AWS Management Console: Go to the EC2 page, choose Load Balancers in the navigation pane, choose the load balancer, choose the Description tab, and get the value of the DNS name field.
If you're routing traffic to a Classic Load Balancer, get the value that begins with dualstack. If you're routing traffic to another type of load balancer, get the value that applies to the record type, A or AAAA.
-
Elastic Load Balancing API: Use
DescribeLoadBalancers
to get the value ofDNSName
. For more information, see the applicable guide:-
Classic Load Balancers: DescribeLoadBalancers
-
Application and Network Load Balancers: DescribeLoadBalancers
-
-
CloudFormation Fn::GetAtt intrinsic function: Use the Fn::GetAtt intrinsic function to get the value of
DNSName
: -
AWS CLI: Use
describe-load-balancers
to get the value ofDNSName
. For more information, see the applicable guide:-
Classic Load Balancers: describe-load-balancers
-
Application and Network Load Balancers: describe-load-balancers
-
-
- Global Accelerator accelerator
-
Specify the DNS name for your accelerator:
Global Accelerator API: To get the DNS name, use DescribeAccelerator.
AWS CLI: To get the DNS name, use describe-accelerator.
- Amazon S3 bucket that is configured as a static website
-
Specify the domain name of the Amazon S3 website endpoint that you created the bucket in, for example,
s3-website.us-east-2.amazonaws.com
. For more information about valid values, see the table Amazon S3 Website Endpoints in the Amazon Web Services General Reference. For more information about using S3 buckets for websites, see Getting Started with Amazon Route 53 in the Amazon Route 53 Developer Guide. - Another Route 53 record
-
Specify the value of the
Name
element for a record in the current hosted zone.Note If you're creating an alias record that has the same name as the hosted zone (known as the zone apex), you can't specify the domain name for a record for which the value of
Type
isCNAME
. This is because the alias record must have the same type as the record that you're routing traffic to, and creating a CNAME record for the zone apex isn't supported even for an alias record.
Required: Yes
Type: String
Maximum:
1024
Update requires: No interruption
EvaluateTargetHealth
-
Applies only to alias, failover alias, geolocation alias, latency alias, and weighted alias resource record sets: When
EvaluateTargetHealth
istrue
, an alias resource record set inherits the health of the referenced AWS resource, such as an ELB load balancer or another resource record set in the hosted zone.Note the following:
- CloudFront distributions
-
You can't set
EvaluateTargetHealth
totrue
when the alias target is a CloudFront distribution. - Elastic Beanstalk environments that have regionalized subdomains
-
If you specify an Elastic Beanstalk environment in
DNSName
and the environment contains an ELB load balancer, Elastic Load Balancing routes queries only to the healthy Amazon EC2 instances that are registered with the load balancer. (An environment automatically contains an ELB load balancer if it includes more than one Amazon EC2 instance.) If you setEvaluateTargetHealth
totrue
and either no Amazon EC2 instances are healthy or the load balancer itself is unhealthy, Route 53 routes queries to other available resources that are healthy, if any.If the environment contains a single Amazon EC2 instance, there are no special requirements.
- ELB load balancers
-
Health checking behavior depends on the type of load balancer:
-
Classic Load Balancers: If you specify an ELB Classic Load Balancer in
DNSName
, Elastic Load Balancing routes queries only to the healthy Amazon EC2 instances that are registered with the load balancer. If you setEvaluateTargetHealth
totrue
and either no EC2 instances are healthy or the load balancer itself is unhealthy, Route 53 routes queries to other resources. -
Application and Network Load Balancers: If you specify an ELB Application or Network Load Balancer and you set
EvaluateTargetHealth
totrue
, Route 53 routes queries to the load balancer based on the health of the target groups that are associated with the load balancer:-
For an Application or Network Load Balancer to be considered healthy, every target group that contains targets must contain at least one healthy target. If any target group contains only unhealthy targets, the load balancer is considered unhealthy, and Route 53 routes queries to other resources.
-
A target group that has no registered targets is considered unhealthy.
-
Note When you create a load balancer, you configure settings for Elastic Load Balancing health checks; they're not Route 53 health checks, but they perform a similar function. Do not create Route 53 health checks for the EC2 instances that you register with an ELB load balancer.
-
- S3 buckets
-
There are no special requirements for setting
EvaluateTargetHealth
totrue
when the alias target is an S3 bucket. - Other records in the same hosted zone
-
If the AWS resource that you specify in
DNSName
is a record or a group of records (for example, a group of weighted records) but is not another alias record, we recommend that you associate a health check with all of the records in the alias target. For more information, see What Happens When You Omit Health Checks? in the Amazon Route 53 Developer Guide.
For more information and examples, see Amazon Route 53 Health Checks and DNS Failover in the Amazon Route 53 Developer Guide.
Required: No
Type: Boolean
Update requires: No interruption
HostedZoneId
-
Alias resource records sets only: The value used depends on where you want to route traffic:
- Amazon API Gateway custom regional APIs and edge-optimized APIs
Specify the hosted zone ID for your API. You can get the applicable value using the AWS CLI command get-domain-names:
-
For regional APIs, specify the value of
regionalHostedZoneId
. -
For edge-optimized APIs, specify the value of
distributionHostedZoneId
.
-
- Amazon Virtual Private Cloud interface VPC endpoint
-
Specify the hosted zone ID for your interface endpoint. You can get the value of
HostedZoneId
using the AWS CLI command describe-vpc-endpoints. - CloudFront distribution
-
Specify
Z2FDTNDATAQYW2
. This is always the hosted zone ID when you create an alias record that routes traffic to a CloudFront distribution.Note Alias records for CloudFront can't be created in a private zone.
- Elastic Beanstalk environment
-
Specify the hosted zone ID for the region that you created the environment in. The environment must have a regionalized subdomain. For a list of regions and the corresponding hosted zone IDs, see AWS Elastic Beanstalk endpoints and quotas in the Amazon Web Services General Reference.
- ELB load balancer
-
Specify the value of the hosted zone ID for the load balancer. Use the following methods to get the hosted zone ID:
-
Service Endpoints table in the "Elastic Load Balancing Endpoints and Quotas" topic in the Amazon Web Services General Reference: Use the value that corresponds with the region that you created your load balancer in. Note that there are separate columns for Application and Classic Load Balancers and for Network Load Balancers.
-
AWS Management Console: Go to the Amazon EC2 page, choose Load Balancers in the navigation pane, select the load balancer, and get the value of the Hosted zone field on the Description tab.
-
Elastic Load Balancing API: Use
DescribeLoadBalancers
to get the applicable value. For more information, see the applicable guide:Classic Load Balancers: Use DescribeLoadBalancers to get the value of
CanonicalHostedZoneNameID
.Application and Network Load Balancers: Use DescribeLoadBalancers to get the value of
CanonicalHostedZoneID
.
-
CloudFormation Fn::GetAtt intrinsic function: Use the Fn::GetAtt intrinsic function to get the applicable value:
Classic Load Balancers: Get CanonicalHostedZoneNameID.
Application and Network Load Balancers: Get CanonicalHostedZoneID.
-
AWS CLI: Use
describe-load-balancers
to get the applicable value. For more information, see the applicable guide:-
Classic Load Balancers: Use describe-load-balancers to get the value of
CanonicalHostedZoneNameID
. -
Application and Network Load Balancers: Use describe-load-balancers to get the value of
CanonicalHostedZoneID
.
-
-
- Global Accelerator accelerator
-
Specify
Z2BJ6XQ5FK7U4H
. - An Amazon S3 bucket configured as a static website
-
Specify the hosted zone ID for the region that you created the bucket in. For more information about valid values, see the table Amazon S3 Website Endpoints in the Amazon Web Services General Reference.
- Another Route 53 record in your hosted zone
-
Specify the hosted zone ID of your hosted zone. (An alias record can't reference a record in a different hosted zone.)
Required: Yes
Type: String
Maximum:
32
Update requires: No interruption
See also
-
Return values in the topic AWS::Route53::RecordSet
AliasTarget in the Amazon Route 53 API Reference


Create and manage your keypad templates, scan the QR code and take the control of your system. You can change the text and images and you're good to go.
You dont need a physical controller anymore, take control of any device with your phone.
Think about your custom desing and implement it easily with our interactive editor.
If you think you have done a great design, share it with other people and get rewards!
The kit comes with two pre-built keypads to help you get started faster. You can change the text and buttons and you're good to go.
Design System
AQUÍ HABLARÉ DEL EDITOR CUANDO ESTÉ HECHO.
AQUÍ HABLARÉ DEL EDITOR CUANDO ESTÉ HECHO
de los botones
del texto
Vinculo para ir al editorGo ahead and create your first template step by step.


Dinn:
You don't have any dinosaur tissue here! Hunt
Pterosaurs, Tyrannosauruses and Velociraptors
and gather samples of their tissue.