text:
Network Working Group | G. Clemm |
Internet-Draft | IBM |
Updates: 4918 (if approved) | J. Crawford |
Intended status: Standards Track | IBM Research |
Expires: January 4, 2008 | J. Reschke, Editor |
greenbytes | |
J. Whitehead | |
U.C. Santa Cruz | |
July 3, 2007 |
By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress".¶
The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt.¶
The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html.¶
This Internet-Draft will expire on January 4, 2008.¶
Copyright © The IETF Trust (2007). All Rights Reserved.¶
This specification defines bindings, and the BIND method for creating multiple bindings to the same resource. Creating a new binding to a resource causes at least one new URI to be mapped to that resource. Servers are required to insure the integrity of any bindings that they allow to be created.¶
Please send comments to the Distributed Authoring and Versioning (WebDAV) working group at <mailto:firstname.lastname@example.com>, which may be joined by sending a message with subject "subscribe" to <mailto:firstname.lastname@example.com>. Discussions of the WEBDAV working group are archived at <http://lists.w3.org/Archives/Public/w3c-dist-auth/>.¶
<http://www.webdav.org/bind/draft-ietf-webdav-bind-issues.html> lists all registered issues since draft 02.¶
I edit (type: edit, status: open) | ||
firstname.lastname@example.com | 2004-05-30 | Umbrella issue for editorial fixes/enhancements. |
Associated changes in this document: B. |
I rfc4918 (type: edit, status: closed) | ||
firstname.lastname@example.com | 2007-06-30 | Update RFC2518bis reference to RFC4918. |
2007-06-30 | Resolution: Done. | |
Associated changes in this document: 1, 1, 1.1, 1.1, 1.2, 2.3, 2.3, 2.4, 2.5, 2.6, 3.1, 4, 8.1, 11, 14.1, A, A, A. |
This specification extends the WebDAV Distributed Authoring Protocol (↓[draft-ietf-webdav-rfc2518bis][RFC4918]) to enable clients to create new access paths to existing resources. This capability is useful for several reasons:¶
URIs of WebDAV-compliant resources are hierarchical and correspond to a hierarchy of collections in resource space. The WebDAV Distributed Authoring Protocol makes it possible to organize these resources into hierarchies, placing them into groupings, known as collections, which are more easily browsed and manipulated than a single flat collection. However, hierarchies require categorization decisions that locate resources at a single location in the hierarchy, a drawback when a resource has multiple valid categories. For example, in a hierarchy of vehicle descriptions containing collections for cars and boats, a description of a combination car/boat vehicle could belong in either collection. Ideally, the description should be accessible from both. Allowing clients to create new URIs that access the existing resource lets them put that resource into multiple collections.¶
Hierarchies also make resource sharing more difficult, since resources that have utility across many collections are still forced into a single collection. For example, the mathematics department at one university might create a collection of information on fractals that contains bindings to some local resources, but also provides access to some resources at other universities. For many reasons, it may be undesirable to make physical copies of the shared resources on the local server: to conserve disk space, to respect copyright constraints, or to make any changes in the shared resources visible automatically. Being able to create new access paths to existing resources in other collections or even on other servers is useful for this sort of case.¶
The BIND method defined here provides a mechanism for allowing clients to create alternative access paths to existing WebDAV resources. HTTP [RFC2616] and WebDAV ↑↓[draft-ietf-webdav-rfc2518bis][RFC4918] methods are able to work because there are mappings between URIs and resources. A method is addressed to a URI, and the server follows the mapping from that URI to a resource, applying the method to that resource. Multiple URIs may be mapped to the same resource, but until now there has been no way for clients to create additional URIs mapped to existing resources.¶
BIND lets clients associate a new URI with an existing WebDAV resource, and this URI can then be used to submit requests to the resource. Since URIs of WebDAV resources are hierarchical, and correspond to a hierarchy of collections in resource space, the BIND method also has the effect of adding the resource to a collection. As new URIs are associated with the resource, it appears in additional collections.¶
A BIND request does not create a new resource, but simply makes available a new URI for submitting requests to an existing resource. The new URI is indistinguishable from any other URI when submitting a request to a resource. Only one round trip is needed to submit a request to the intended target. Servers are required to enforce the integrity of the relationships between the new URIs and the resources associated with them. Consequently, it may be very costly for servers to support BIND requests that cross server boundaries.¶
This specification is organized as follows. Section 1.1 defines terminology used in the rest of the specification, while Section 2 overviews bindings. Section 3 defines the new properties needed to support multiple bindings to the same resource. Section 4 specifies the BIND method, used to create multiple bindings to the same resource. Section 5 specifies the UNBIND method, used to remove a binding to a resource. Section 6 specifies the REBIND method, used to move a binding to another collection.¶
The terminology used here follows and extends that in the WebDAV Distributed Authoring Protocol specification ↑↓[draft-ietf-webdav-rfc2518bis][RFC4918].¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].¶
This document uses XML DTD fragments ([XML]) as a notational convention, using the rules defined in ↑↓Section 17 of [draft-ietf-webdav-rfc2518bis]Section 17 of [RFC4918].¶
URI Mapping ¶
Path Segment ¶
Binding ¶
Collection ¶
Internal Member URI ¶
See ↑↓Section 16 of [draft-ietf-webdav-rfc2518bis]Section 16 of [RFC4918] for the definitions of "precondition" and "postcondition".¶
Bindings are part of the state of a collection. They define the internal members of the collection, and the names of those internal members.¶
Bindings are added and removed by a variety of existing HTTP methods. A method that creates a new resource, such as PUT, COPY, and MKCOL, adds a binding. A method that deletes a resource, such as DELETE, removes a binding. A method that moves a resource (e.g. MOVE) both adds a binding (in the destination collection) and removes a binding (in the source collection). The BIND method introduced here provides a mechanism for adding a second binding to an existing resource. There is no difference between an initial binding added by PUT, COPY, or MKCOL, and additional bindings added with BIND.¶
It would be very undesirable if one binding could be destroyed as a side effect of operating on the resource through a different binding. In particular, the removal of one binding to a resource (e.g. with a DELETE or a MOVE) MUST NOT disrupt another binding to that resource, e.g. by turning that binding into a dangling path segment. The server MUST NOT reclaim system resources after removing one binding, while other bindings to the resource remain. In other words, the server MUST maintain the integrity of a binding. It is permissible, however, for future method definitions (e.g., a DESTROY method) to have semantics that explicitly remove all bindings and/or immediately reclaim system resources.¶
Creating a new binding to a collection makes each resource associated with a binding in that collection accessible via a new URI, and thus creates new URI mappings to those resources but no new bindings.¶
For example, suppose a new binding CollY is created for collection C1 in the figure below. It immediately becomes possible to access resource R1 using the URI /CollY/x.gif and to access resource R2 using the URI /CollY/y.jpg, but no new bindings for these child resources were created. This is because bindings are part of the state of a collection, and associate a URI that is relative to that collection with its target resource. No change to the bindings in Collection C1 is needed to make its children accessible using /CollY/x.gif and /CollY/y.jpg.¶
┌─────────────────────────┐ │ Root Collection │ │ bindings: │ │ CollX CollY │ └─────────────────────────┘ | / | / | / ┌──────────────────┐ │ Collection C1 │ │ bindings: │ │ x.gif y.jpg │ └──────────────────┘ | \ | \ | \ ┌─────────────┐ ┌─────────────┐ │ Resource R1 │ │ Resource R2 │ └─────────────┘ └─────────────┘
Bindings to collections can result in loops, which servers MUST detect when processing "Depth: infinity" requests. It is sometimes possible to complete an operation in spite of the presence of a loop. For instance, a PROPFIND can still succeed if the server uses the new status code 208 (Already Reported) defined in Section 7.1.¶
However, the 506 (Loop Detected) status code is defined in Section 7.2 for use in contexts where an operation is terminated because a loop was encountered.¶
Suppose a binding from "Binding-Name" to resource R is to be added to a collection, C. Then if C-MAP is the set of URIs that were mapped to C before the BIND request, then for each URI "C-URI" in C-MAP, the URI "C-URI/Binding-Name" is mapped to resource R following the BIND request.¶
For example, if a binding from "foo.html" to R is added to a collection C, and if the following URIs are mapped to C:
http://www.example.com/A/1/ http://example.com/A/one/
then the following new mappings to R are introduced:
http://www.example.com/A/1/foo.html http://example.com/A/one/foo.html
Note that if R is a collection, additional URI mappings are created to the descendents of R. Also, note that if a binding is made in collection C to C itself (or to a parent of C), an infinite number of mappings are introduced.¶
For example, if a binding from "myself" to C is then added to C, the following infinite number of additional mappings to C are introduced:
http://www.example.com/A/1/myself http://www.example.com/A/1/myself/myself ...
and the following infinite number of additional mappings to R are introduced:
http://www.example.com/A/1/myself/foo.html http://www.example.com/A/1/myself/myself/foo.html ...
As defined in ↑↓Section 9.8 of [draft-ietf-webdav-rfc2518bis]Section 9.8 of [RFC4918], COPY causes the resource identified by the Request-URI to be duplicated, and makes the new resource accessible using the URI specified in the Destination header. Upon successful completion of a COPY, a new binding is created between the last path segment of the Destination header, and the destination resource. The new binding is added to its parent collection, identified by the Destination header minus its final segment.¶
The following figure shows an example: Suppose that a COPY is issued to URI-3 for resource R (which is also mapped to URI-1 and URI-2), with the Destination header set to URI-X. After successful completion of the COPY operation, resource R is duplicated to create resource R', and a new binding has been created which creates at least the URI mapping between URI-X and the new resource (although other URI mappings may also have been created).
URI-1 URI-2 URI-3 URI-X | | | | | | | <---- URI Mappings ----> | | | | | ┌─────────────────────┐ ┌────────────────────────┐ │ Resource R │ │ Resource R' │ └─────────────────────┘ └────────────────────────┘
It might be thought that a COPY request with "Depth: 0" on a collection would duplicate its bindings, since bindings are part of the collection's state. This is not the case, however. The definition of Depth in ↑↓[draft-ietf-webdav-rfc2518bis][RFC4918] makes it clear that a "Depth: 0" request does not apply to a collection's members. Consequently, a COPY with "Depth: 0" does not duplicate the bindings contained by the collection.¶
If a COPY request causes an existing resource to be updated, the bindings to that resource MUST be unaffected by the COPY request. Using the preceding example, suppose that a COPY request is issued to URI-X for resource R', with the Destination header set to URI-2. The content and dead properties of resource R would be updated to be a copy of those of resource R', but the mappings from URI-1, URI-2, and URI-3 to resource R remain unaffected. If because of multiple bindings to a resource, more than one source resource updates a single destination resource, the order of the updates is server defined.¶
If a COPY request would cause a new resource to be created as a copy of an existing resource, and that COPY request has already created a copy of that existing resource, the COPY request instead creates another binding to the previous copy, instead of creating a new resource.¶
As an example of how COPY with Depth infinity would work in the presence of bindings, consider the following collection:
┌──────────────────┐ │ Root Collection │ │ bindings: │ │ CollX │ └──────────────────┘ | | ┌───────────────────────────────┐ │ Collection C1 │<-------+ │ bindings: │ | │ x.gif CollY │ | └───────────────────────────────┘ | | \ (creates loop) | | \ | ┌─────────────┐ ┌──────────────────┐ | │ Resource R1 │ │ Collection C2 │ | └─────────────┘ │ bindings: │ | │ y.gif CollZ │ | └──────────────────┘ | | | | | +--------+ | ┌─────────────┐ │ Resource R2 │ └─────────────┘
If a COPY with Depth infinity is submitted to /CollX, with destination of /CollA, the outcome of the copy operation is:
┌──────────────────┐ │ Root Collection │ │ bindings: │ │ CollX CollA │ └──────────────────┘ | | | +---------------------------+ | | ┌───────────────────┐ | │ Collection C1 │<------------------+ | │ bindings: │ | | │ x.gif CollY │ | | └───────────────────┘ | | | \ (creates loop) | | | \ | | ┌─────────────┐ ┌─────────────────┐ | | │ Resource R1 │ │ Collection C2 │ | | └─────────────┘ │ bindings: │ | | │ y.gif CollZ │ | | └─────────────────┘ | | | | | | | +-------+ | | | ┌─────────────┐ | │ Resource R2 │ | └─────────────┘ | | +-------------------------------+ | ┌───────────────────┐ │ Collection C3 │<------------------+ │ bindings: │ | │ x.gif CollY │ | └───────────────────┘ | | \ (creates loop) | | \ | ┌─────────────┐ ┌─────────────────┐ | │ Resource R3 │ │ Collection C4 │ | └─────────────┘ │ bindings: │ | │ y.gif CollZ │ | └─────────────────┘ | | | | | +-------+ | ┌─────────────┐ │ Resource R4 │ └─────────────┘
Given the following collection hierarchy:
┌──────────────────┐ │ Root Collection │ │ bindings: │ │ CollX │ └──────────────────┘ | | | ┌────────────────┐ │ Collection C1 │ │ bindings: │ │ x.gif y.gif │ └────────────────┘ | | | | ┌─────────────┐ │ Resource R1 │ └─────────────┘
A COPY of /CollX with Depth infinity to /CollY results in the following collection hierarchy:
┌──────────────────┐ │ Root Collection │ │ bindings: │ │ CollX CollY │ └──────────────────┘ | \ | \ | \ ┌────────────────┐ ┌─────────────────┐ │ Collection C1 │ │ Collection C2 │ │ bindings: │ │ bindings: │ │ x.gif y.gif │ │ x.gif y.gif │ └────────────────┘ └─────────────────┘ | | | | | | | | ┌─────────────┐ ┌─────────────┐ │ Resource R1 │ │ Resource R2 │ └─────────────┘ └─────────────┘
When there are multiple bindings to a resource, a DELETE applied to that resource MUST NOT remove any bindings to that resource other than the one identified by the Request-URI. For example, suppose the collection identified by the URI "/a" has a binding named "x" to a resource R, and another collection identified by "/b" has a binding named "y" to the same resource R. Then a DELETE applied to "/a/x" removes the binding named "x" from "/a" but MUST NOT remove the binding named "y" from "/b" (i.e. after the DELETE, "/y/b" continues to identify the resource R).¶
When DELETE is applied to a collection, it MUST NOT modify the membership of any other collection that is not itself a member of the collection being deleted. For example, if both "/a/.../x" and "/b/.../y" identify the same collection, C, then applying DELETE to "/a" must not delete an internal member from C or from any other collection that is a member of C, because that would modify the membership of "/b".¶
If a collection supports the UNBIND method (see Section 5), a DELETE of an internal member of a collection MAY be implemented as an UNBIND request. In this case, applying DELETE to a Request-URI has the effect of removing the binding identified by the final segment of the Request-URI from the collection identified by the Request-URI minus its final segment. Although ↑↓[draft-ietf-webdav-rfc2518bis][RFC4918] allows a DELETE to be a non-atomic operation, when the DELETE operation is implemented as an UNBIND, the operation is atomic. In particular, a DELETE on a hierarchy of resources is simply the removal of a binding to the collection identified by the Request-URI.¶
When MOVE is applied to a resource, the other bindings to that resource MUST be unaffected, and if the resource being moved is a collection, the bindings to any members of that collection MUST be unaffected. Also, if MOVE is used with Overwrite:T to delete an existing resource, the constraints specified for DELETE apply.¶
If the destination collection of a MOVE request supports the REBIND method (see Section 6), a MOVE of a resource into that collection MAY be implemented as a REBIND request. Although ↑↓[draft-ietf-webdav-rfc2518bis][RFC4918] allows a MOVE to be a non-atomic operation, when the MOVE operation is implemented as a REBIND, the operation is atomic. In particular, applying a MOVE to a Request-URI and a Destination URI has the effect of removing a binding to a resource (at the Request-URI), and creating a new binding to that resource (at the Destination URI). Even when the Request-URI identifies a collection, the MOVE operation involves only removing one binding to that collection and adding another.¶
As an example, suppose that a MOVE is issued to URI-3 for resource R below (which is also mapped to URI-1 and URI-2), with the Destination header set to URI-X. After successful completion of the MOVE operation, a new binding has been created which creates the URI mapping between URI-X and resource R. The binding corresponding to the final segment of URI-3 has been removed, which also causes the URI mapping between URI-3 and R to be removed. If resource R were a collection, old URI-3 based mappings to members of R would have been removed, and new URI-X based mappings to members of R would have been created.¶
>> Before Request:
URI-1 URI-2 URI-3 | | | | | | <---- URI Mappings | | | ┌─────────────────────┐ │ Resource R │ └─────────────────────┘
>> After Request:
URI-1 URI-2 URI-X | | | | | | <---- URI Mappings | | | ┌─────────────────────┐ │ Resource R │ └─────────────────────┘
Consistent with ↑↓[draft-ietf-webdav-rfc2518bis][RFC4918], the value of a dead property MUST be independent of the number of bindings to its host resource or of the path submitted to PROPFIND. On the other hand, the behaviour for each live property depends on its individual definition (for example, see [RFC3744], Section 5, paragraph 2).¶
It is useful to have some way of determining whether two bindings are to the same resource. Two resources might have identical contents and properties, but not be the same resource (e.g. an update to one resource does not affect the other resource).¶
The REQUIRED DAV:resource-id property defined in Section 3.1 is a resource identifier, which MUST be unique across all resources for all time. If the values of DAV:resource-id returned by PROPFIND requests through two bindings are identical character by character, the client can be assured that the two bindings are to the same resource.¶
The DAV:resource-id property is created, and its value assigned, when the resource is created. The value of DAV:resource-id MUST NOT be changed. Even after the resource is no longer accessible through any URI, that value MUST NOT be reassigned to another resource's DAV:resource-id property.¶
Any method that creates a new resource MUST assign a new, unique value to its DAV:resource-id property. For example, a PUT applied to a null resource, COPY (when not overwriting an existing target) and CHECKIN (see [RFC3253], Section 4.4) must assign a new, unique value to the DAV:resource-id property of the new resource they create.¶
On the other hand, any method that affects an existing resource must not change the value of its DAV:resource-id property. Specifically, a PUT or a COPY that updates an existing resource must not change the value of its DAV:resource-id property. A REBIND, since it does not create a new resource, but only changes the location of an existing resource, must not change the value of the DAV:resource-id property.¶
An OPTIONAL DAV:parent-set property on a resource provides a list of the bindings that associate a collection and a URI segment with that resource. If the DAV:parent-set property exists on a given resource, it MUST contain a complete list of all bindings to that resource that the client is authorized to see. When deciding whether to support the DAV:parent-set property, server implementers / administrators should balance the benefits it provides against the cost of maintaining the property and the security risks enumerated in Sections 10.4 and 10.5.¶
The bind feature introduces the properties defined below.¶
A DAV:allprop PROPFIND request SHOULD NOT return any of the properties defined by this document. This allows a binding server to perform efficiently when a naive client, which does not understand the cost of asking a server to compute all possible live properties, issues a DAV:allprop PROPFIND request.¶
The DAV:resource-id property is a REQUIRED property that enables clients to determine whether two bindings are to the same resource. The value of DAV:resource-id is a URI, and may use any registered URI scheme that guarantees the uniqueness of the value across all resources for all time (e.g. the urn:uuid: URN namespace defined in [RFC4122] or the opaquelocktoken: URI scheme defined in ↑↓[draft-ietf-webdav-rfc2518bis][RFC4918]).¶
<!ELEMENT resource-id (href)>
The DAV:parent-set property is an OPTIONAL property that enables clients to discover what collections contain a binding to this resource (i.e. what collections have that resource as an internal member). It contains an of href/segment pair for each collection that has a binding to the resource. The href identifies the collection, and the segment identifies the binding name of that resource in that collection.¶
A given collection MUST appear only once in the DAV:parent-set for any given binding, even if there are multiple URI mappings to that collection.¶
<!ELEMENT parent-set (parent)*> <!ELEMENT parent (href, segment)> <!ELEMENT segment (#PCDATA)> <!-- PCDATA value: segment, as defined in Section 3.3 [RFC3986] -->
For example, if collection C1 is mapped to both /CollX and /CollY, and C1 contains a binding named "x.gif" to a resource R1, then either [/CollX, x.gif] or [/CollY, x.gif] can appear in the DAV:parent-set of R1, but not both. But if C1 also had a binding named "y.gif" to R1, then there would be two entries for C1 in the DAV:binding-set of R1 (i.e. both [/CollX, x.gif] and [/CollX, y.gif] or, alternatively, both [/CollY, x.gif] and [/CollY, y.gif]).¶
┌─────────────────────────┐ │ Root Collection │ │ bindings: │ │ CollX CollY │ └─────────────────────────┘ | / | / | / ┌─────────────────┐ │ Collection C1 │ │ bindings: │ │ x.gif y.gif │ └─────────────────┘ | | | | | | ┌──────────────┐ │ Resource R1 │ └──────────────┘
In this case, one possible value for DAV:parent-set property on "/CollX/x.gif" would be:¶
<parent-set xmlns="DAV:"> <parent> <href>/CollX</href> <segment>x.gif</segment> </parent> <parent> <href>/CollX</href> <segment>y.gif</segment> </parent> </parent-set>
The BIND method modifies the collection identified by the Request-URI, by adding a new binding from the segment specified in the BIND body to the resource identified in the BIND body.¶
If a server cannot guarantee the integrity of the binding, the BIND request MUST fail. Note that it is especially difficult to maintain the integrity of cross-server bindings. Unless the server where the resource resides knows about all bindings on all servers to that resource, it may unwittingly destroy the resource or make it inaccessible without notifying another server that manages a binding to the resource. For example, if server A permits creation of a binding to a resource on server B, server A must notify server B about its binding and must have an agreement with B that B will not destroy the resource while A's binding exists. Otherwise server B may receive a DELETE request that it thinks removes the last binding to the resource and destroy the resource while A's binding still exists. The precondition DAV:cross-server-binding is defined below for cases where servers fail cross-server BIND requests because they cannot guarantee the integrity of cross-server bindings.¶
By default, if there already is a binding for the specified segment in the collection, the new binding replaces the existing binding. This default binding replacement behavior can be overridden using the Overwrite header defined in ↑↓Section 10.6 of [draft-ietf-webdav-rfc2518bis]Section 10.6 of [RFC4918].¶
If a BIND request fails, the server state preceding the request MUST be restored. This method is unsafe and idempotent (see [RFC2616], Section 9.1).¶
Marshalling: ¶
<!ELEMENT bind (segment, href)>
<!ELEMENT bind-response ANY>
Preconditions: ¶
Postconditions: ¶
>> Request:
BIND /CollY HTTP/1.1 Host: www.example.com Content-Type: application/xml; charset="utf-8" Content-Length: xxx <?xml version="1.0" encoding="utf-8" ?> <D:bind xmlns:D="DAV:"> <D:segment>bar.html</D:segment> <D:href>http://www.example.com/CollX/foo.html</D:href> </D:bind>
>> Response:
HTTP/1.1 201 Created
The server added a new binding to the collection, "http://www.example.com/CollY", associating "bar.html" with the resource identified by the URI "http://www.example.com/CollX/foo.html". Clients can now use the URI "http://www.example.com/CollY/bar.html" to submit requests to that resource.¶
The UNBIND method modifies the collection identified by the Request-URI, by removing the binding identified by the segment specified in the UNBIND body.¶
Once a resource is unreachable by any URI mapping, the server MAY reclaim system resources associated with that resource. If UNBIND removes a binding to a resource, but there remain URI mappings to that resource, the server MUST NOT reclaim system resources associated with the resource.¶
If an UNBIND request fails, the server state preceding the request MUST be restored. This method is unsafe and idempotent (see [RFC2616], Section 9.1).¶
Marshalling: ¶
<!ELEMENT unbind (segment)>
<!ELEMENT unbind-response ANY>
Preconditions: ¶
Postconditions: ¶
>> Request:
UNBIND /CollX HTTP/1.1 Host: www.example.com Content-Type: application/xml; charset="utf-8" Content-Length: xxx <?xml version="1.0" encoding="utf-8" ?> <D:unbind xmlns:D="DAV:"> <D:segment>foo.html</D:segment> </D:unbind>
>> Response:
The server removed the binding named "foo.html" from the collection, "http://www.example.com/CollX". A request to the resource named "http://www.example.com/CollX/foo.html" will return a 404 (Not Found) response.¶
The REBIND method removes a binding to a resource from a collection, and adds a binding to that resource into the collection identified by the Request-URI. The request body specifies the binding to be added (segment) and the old binding to be removed (href). It is effectively an atomic form of a MOVE request, and MUST be treated the same way as MOVE for the purpose of determining access permissions.¶
If a REBIND request fails, the server state preceding the request MUST be restored. This method is unsafe and idempotent (see [RFC2616], Section 9.1).¶
Marshalling: ¶
<!ELEMENT rebind (segment, href)>
<!ELEMENT rebind-response ANY>
Preconditions: ¶
Postconditions: ¶
>> Request:
REBIND /CollX HTTP/1.1 Host: www.example.com Content-Type: application/xml; charset="utf-8" Content-Length: xxx <?xml version="1.0" encoding="utf-8" ?> <D:rebind xmlns:D="DAV:"> <D:segment>foo.html</D:segment> <D:href>http://www.example.com/CollY/bar.html</D:href> </D:rebind>
>> Response:
The server added a new binding to the collection, "http://www.example.com/CollX", associating "foo.html" with the resource identified by the URI "http://www.example.com/CollY/bar.html", and removes the binding named "bar.html" from the collection identified by the URI "http://www.example.com/CollY". Clients can now use the URI "http://www.example.com/CollX/foo.html" to submit requests to that resource, and requests on the URI "http://www.example.com/CollY/bar.html" will fail with a 404 (Not Found) response.¶
To illustrate the effects of locks and bind loops on a REBIND operation, consider the following collection:
┌──────────────────┐ │ Root Collection │ │ bindings: │ │ CollW │ └──────────────────┘ | | | ┌───────────────────────────────┐ │ Collection C1 │<--------+ │ LOCKED infinity │ | │ (lock token L1) │ | │ bindings: │ | │ CollX CollY │ | └───────────────────────────────┘ | | | | | | (creates loop) | | | | ┌─────────────────┐ ┌──────────────────┐ | │ Collection C2 │ │ Collection C3 │ | │ (inherit lock) │ │ (inherit lock) │ | │ (lock token L1) │ │ (lock token L1) │ | │ bindings: │ │ bindings: │ | │ {none} │ │ y.gif CollZ │ | └─────────────────┘ └──────────────────┘ | | | | | +-----+ | ┌───────────────────────────┐ │ Resource R2 │ │ (lock inherited from C1) │ │ (lock token L1) │ └───────────────────────────┘
(where L1 is "opaquelocktoken:f92d4fae-7012-11ab-a765-00c0ca1f6bf9").
Note that the binding between CollZ and C1 creates a loop in the containment hierarchy. Servers are not required to support such loops, though the server in this example does.¶
The REBIND request below will remove the segment "CollZ" from C3 and add a new binding from "CollA" to the collection C2.
REBIND /CollW/CollX HTTP/1.1 Host: www.example.com If: (<opaquelocktoken:f92d4fae-7012-11ab-a765-00c0ca1f6bf9>) Content-Type: application/xml; charset="utf-8" Content-Length: xxx <?xml version="1.0" encoding="utf-8" ?> <D:rebind xmlns:D="DAV:"> <D:segment>CollA</D:segment> <D:href>/CollW/CollY/CollZ</D:href> </D:rebind>
The outcome of the REBIND operation is:
┌──────────────────┐ │ Root Collection │ │ bindings: │ │ CollW │ └──────────────────┘ | | | ┌───────────────────────────────┐ │ Collection C1 │ │ LOCKED infinity │ │ (lock token L1) │ │ bindings: │ │ CollX CollY │ └───────────────────────────────┘ | ^ | | | | ┌─────────────────┐ | ┌──────────────────┐ │ Collection C2 │ | │ Collection C3 │ │(inherited lock) │ | │ (inherited lock) │ │(lock token L1) │ | │ (lock token L1) │ │ bindings: │ | │ bindings: │ │ CollA │ | │ y.gif │ └─────────────────┘ | └──────────────────┘ | | | +---------------+ | (creates loop) | ┌───────────────────────────┐ │ Resource R2 │ │ (inherited lock from C1) │ │ (lock token L1) │ └───────────────────────────┘
The 208 (Already Reported) status code can be used inside a DAV:propstat response element to avoid enumerating the internal members of multiple bindings to the same collection repeatedly. For each binding to a collection inside the request's scope, only one will be reported with a 200 status, while subsequent DAV:response elements for all other bindings will use the 208 status, and no DAV:response elements for their descendants are included.¶
Note that the 208 status will only occur for "Depth: infinity" requests, and that it is of particular importance when the multiple collection bindings cause a bind loop as discussed in Section 2.2.¶
A client can request the DAV:resource-id property in a PROPFIND request to guarantee that they can accurately reconstruct the binding structure of a collection with multiple bindings to a single resource.¶
For backward compatibility with clients not aware of the 208 status code appearing in multistatus response bodies, it SHOULD NOT be used unless the client has signalled support for this specification using the "DAV" request header (see Section 8.2). Instead, a 506 status should be returned when a binding loop is discovered. This allows the server to return the 506 as the top level return status, if it discovers it before it started the response, or in the middle of a multistatus, if it discovers it in the middle of streaming out a multistatus response.¶
For example, consider a PROPFIND request on /Coll (bound to collection C), where the members of /Coll are /Coll/Foo (bound to resource R) and /Coll/Bar (bound to collection C).¶
>> Request:
PROPFIND /Coll/ HTTP/1.1 Host: www.example.com Depth: infinity DAV: bind Content-Type: application/xml; charset="utf-8" Content-Length: xxx <?xml version="1.0" encoding="utf-8" ?> <D:propfind xmlns:D="DAV:"> <D:prop> <D:displayname/> <D:resource-id/> </D:prop> </D:propfind>
>> Response:
HTTP/1.1 207 Multi-Status Content-Type: application/xml; charset="utf-8" Content-Length: xxx <?xml version="1.0" encoding="utf-8" ?> <D:multistatus xmlns:D="DAV:"> <D:response> <D:href>http://www.example.com/Coll/</D:href> <D:propstat> <D:prop> <D:displayname>Loop Demo</D:displayname> <D:resource-id> <D:href >urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf8</D:href> </D:resource-id> </D:prop> <D:status>HTTP/1.1 200 OK</D:status> </D:propstat> </D:response> <D:response> <D:href>http://www.example.com/Coll/Foo</D:href> <D:propstat> <D:prop> <D:displayname>Bird Inventory</D:displayname> <D:resource-id> <D:href >urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf9</D:href> </D:resource-id> </D:prop> <D:status>HTTP/1.1 200 OK</D:status> </D:propstat> </D:response> <D:response> <D:href>http://www.example.com/Coll/Bar</D:href> <D:propstat> <D:prop> <D:displayname>Loop Demo</D:displayname> <D:resource-id> <D:href >urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf8</D:href> </D:resource-id> </D:prop> <D:status>HTTP/1.1 208 Already Reported</D:status> </D:propstat> </D:response> </D:multistatus>
In this example, the client isn't aware of the 208 status code introduced by this specification. As the "Depth: infinity" PROPFIND request would cause a loop condition, the whole request is rejected with a 506 status.¶
>> Request:
PROPFIND /Coll/ HTTP/1.1 Host: www.example.com Depth: infinity Content-Type: application/xml; charset="utf-8" Content-Length: xxx <?xml version="1.0" encoding="utf-8" ?> <D:propfind xmlns:D="DAV:"> <D:prop> <D:displayname/> </D:prop> </D:propfind>
>> Response:
HTTP/1.1 506 Loop Detected
The 506 (Loop Detected) status code indicates that the server terminated an operation because it encountered an infinite loop while processing a request with "Depth: infinity". This status indicates that the entire operation failed.¶
If the server supports bindings, it MUST return the compliance class name "bind" as a field in the "DAV" response header (see ↑↓[draft-ietf-webdav-rfc2518bis], Section 10.1[RFC4918], Section 10.1) from an OPTIONS request on any resource implemented by that server. A value of "bind" in the "DAV" header MUST indicate that the server supports all MUST level requirements and REQUIRED features specified in this document.¶
Clients SHOULD signal support for all MUST level requirements and REQUIRED features by submitting a "DAV" request header containing the compliance class name "bind". In particular, the client MUST understand the 208 status code defined in Section 7.1.¶
BIND and REBIND behave the same as MOVE with respect to the DAV:acl property (see [RFC3744], Section 7.3).¶
This section is provided to make WebDAV implementors aware of the security implications of this protocol.¶
All of the security considerations of HTTP/1.1 and the WebDAV Distributed Authoring Protocol specification also apply to this protocol specification. In addition, bindings introduce several new security concerns and increase the risk of some existing threats. These issues are detailed below.¶
In a context where cross-server bindings are supported, creating bindings on a trusted server may make it possible for a hostile agent to induce users to send private information to a target on a different server.¶
Although bind loops were already possible in HTTP 1.1, the introduction of the BIND method creates a new avenue for clients to create loops accidentally or maliciously. If the binding and its target are on the same server, the server may be able to detect BIND requests that would create loops. Servers are required to detect loops that are caused by bindings to collections during the processing of any requests with "Depth: infinity".¶
Denial of service attacks were already possible by posting URIs that were intended for limited use at heavily used Web sites. The introduction of BIND creates a new avenue for similar denial of service attacks. If cross-server bindings are supported, clients can now create bindings at heavily used sites to target locations that were not designed for heavy usage.¶
If the DAV:parent-set property is maintained on a resource, the owners of the bindings risk revealing private locations. The directory structures where bindings are located are available to anyone who has access to the DAV:parent-set property on the resource. Moving a binding may reveal its new location to anyone with access to DAV:parent-set on its resource.¶
If the server maintains the DAV:parent-set property in response to bindings created in other administrative domains, it is exposed to hostile attempts to make it devote resources to adding bindings to the list.¶
All internationalization considerations mentioned in ↑↓[draft-ietf-webdav-rfc2518bis][RFC4918] also apply to this document.¶
Section 7 defines the HTTP status codes 208 (Already Reported) and 506 (Loop Detected), to be added to the registry at <http://www.iana.org/assignments/http-status-codes>.¶
This document is the collaborative product of the authors and Tyson Chihaya, Jim Davis, Chuck Fay and Judith Slein. This draft has benefited from thoughtful discussion by Jim Amsden, Peter Carlson, Steve Carter, Ken Coar, Ellis Cohen, Dan Connolly, Bruce Cragun, Spencer Dawkins, Mark Day, Rajiv Dulepet, David Durand, Lisa Dusseault, Stefan Eissing, Roy Fielding, Yaron Goland, Joe Hildebrand, Fred Hitt, Alex Hopmann, James Hunt, Marcus Jager, Chris Kaler, Manoj Kasichainula, Rohit Khare, Brian Korver, Daniel LaLiberte, Steve Martin, Larry Masinter, Jeff McAffer, Surendra Koduru Reddy, Max Rible, Sam Ruby, Bradley Sergeant, Nick Shelness, John Stracke, John Tigue, John Turner, Kevin Wiggen, and other members of the WebDAV working group.¶
A LOCK request to an existing resource will create a lock on the resource identified by the Request-URI, provided the resource is not already locked with a conflicting lock. The resource identified in the Request-URI becomes the root of the lock.¶
This is incorrect in that it implies that the "lock root" is a resource, not a URL (<http://ietf.osafoundation.org:8080/bugzilla/show_bug.cgi?id=251>). However, should a directly locked resource have multiple bindings, only the one used in the Request-URI of the LOCK request will be the protected from changes of clients not supplying the lock token.¶
A correct description would be: ¶
Note that this change makes the description consistent with the definition of the DAV:lockroot XML element in ↑↓Section 14.12 of [draft-ietf-webdav-rfc2518bis]Section 14.12 of [RFC4918].¶
The authors of this specification recommend that future revisions of ↑[draft-ietf-webdav-rfc2518bis][RFC4918] will update the description as suggested above.¶
Add and resolve issues "2.3_COPY_SHARED_BINDINGS" and "2.3_MULTIPLE_COPY". Add issue "5.1_LOOP_STATUS" and proposed resolution, but keep it open. Add issues "ED_references" and "4_507_status". Started work on index. Rename document to "Binding Extensions to Web Distributed Authoring and Versioning (WebDAV)". Rename "References" to "Normative References". Close issue "ED_references". Close issue "4_507_status".¶
Add and close issues "9.2_redirect_loops", "ED_authors" and "ED_updates". Add section about capability discovery (DAV header). Close issues "5.1_LOOP_STATUS". Add and resolve new issue "5.1_506_STATUS_STREAMING". Update XML spec reference. Add issue "locking" and resolve as invalid.¶
Add and close issues "6_precondition_binding_allowed" and "6_lock_behaviour". Add mailing list and issues list pointers to front.¶
Editorial fixes. Add and resolve issues "1.3_error_negotiation", "2.5_language" and "7.1.1_add_resource_id". Add historical issue "4_LOCK_BEHAVIOR" and it's resolution for better tracking.¶
Rewrite Editorial Note. Open and resolve issues "2.6_identical", "specify_safeness_and_idempotence" and "ED_rfc2026_ref".¶
Add more index items (no change tracking). Add and resolve issues "2.3_copy_to_same", "bind_properties", "bind_vs_ACL", "6_rebind_intro" and "rfc2396bis" (actually an action item). Fix XML DTD fragment in section 3.3. Make spelling of "Request-URI" consistent.¶
Resolved editorial issues raised by Jim Whitehead in <http://lists.w3.org/Archives/Public/w3c-dist-auth/2004OctDec/0129.html>. Add and resolve issues "atomicity", "2_allow_destroy", "2.1_separate_loop_discussion", "2.1.1_bind_loops_vs_locks", "2.3_copy_depth_infinity", "2.3_copy_example", "2.3_copy_vs_loops", "2.6_resource-id_vs_versions", "3.2_example" and "6_rebind_premissions". Add issue "2.6_when_do_ids_change". Re-open and resolve "6_rebind_intro".¶
Add and resolve issue "6.1_rebind_vs_locks", adding proposed example text. Add action item "3.1_uuids". Close issue "2.6_when_do_ids_change". Add and resolve issues "2.6_bindings_vs_properties" and "uri_draft_ref".¶
Resolve action item "3.1_uuids". Add and resolve issue "2.7_unlock_vs_bindings". Revisit issue "2.6_bindings_vs_properties", and remove the part of the sentence that speaks about live properties. Update "rfc2396bis" references to "RFC3986". Add issue "9_ns_op_and_acl" and add potential resolution. Align artwork where applicable (new xml2rfc1.29rc2 feature).¶
Updated [draft-mealling-uuid-urn] to [RFC4122]. Add statement about live properties in Section 2.6.¶
Updated Author's address. Uppercase "Section" when referring to other documents.¶
Updating from RFC2518 to RFC2518bis: ¶
Update [draft-ietf-webdav-rfc2518-bis] to draft 14. Update one incorrect section reference. Remove Section "Rationale for Distinguishing Bindings from URI Mappings" as [draft-ietf-webdav-rfc2518-bis] now uses the proper definition of collection state. Examples use application/xml instead of text/xml MIME type.¶
Fix IANA section (there are no IANA considerations).¶
Update [draft-ietf-webdav-rfc2518-bis] to draft 15. Update [XML] to 4th edition.¶
Markup ASCII art for box recognition (doesn't affect ASCII version).¶
Identify Julian Reschke as Editor.¶
Fix typo in RFC2119 keywords section (sorry!).¶
Update [draft-ietf-webdav-rfc2518-bis] to draft 17.¶
Add and resolve issue "rfc2518bis-lock-root".¶
Add and resolve issue "iana-vs-http-status".¶
Update rfc2518bis reference to draft 18 (note that the bug reported in <http://ietf.osafoundation.org:8080/bugzilla/show_bug.cgi?id=251> is still present).¶
Update: draft-ietf-webdav-rfc2518bis replaced by RFC4918.
Copyright © The IETF Trust (2007).¶
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.¶
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.¶
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.¶
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.¶
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at email@example.com.¶


text:
Tech giant Google announced Tuesday that it has begun offering free public WiFi internet access in the southwest Chelsea neighborhood of New York City, close to its mammoth headquarters. According to Google, the new service — which was the product of a public-private effort by the company, city officials, and a local nonprofit development ogranization — will provide free Internet access to hundreds of thousands of people each year, making it the largest such WiFi network in New York City.
Google said that free WiFi is now available — today — outdoors, "roughly between Gansevoort St. and 19 St. from 8th Ave to the West Side Highway, as well as the neighborhood's public spaces, including the Chelsea Triangle, 14th Street Park, and Gansevoort Plaza." The WiFi network will not require a password.
"Google is proud to provide free WiFi in the neighborhood we have called home for over six years," Ben Fried, the company's chief information officer, said in a statement. "This network will not only be a resource for the 2,000+ residents of the Fulton Houses, it will also serve the 5,000+ student population of Chelsea as well as the hundreds of workers, retail customers and tourists who visit our neighborhood every day."
(MORE: Is Broadband Internet Access a Public Utility like Electricity and Water?)
New York officials praised Google's move, calling it a another step toward the city's ambitious goal of becoming one of the most important technology hubs in the world.
"New York is determined to become the world's leading digital city, and universal access to high-speed Internet is one of the core building blocks of that vision," New York City Mayor Michael Bloomberg said in a statement. "Thanks to Google, free WiFi across this part of Chelsea takes us another step closer to that goal." At a press conference, Bloomberg said that he'd ultimately like to see similar WiFi service throughout the city.
Since moving into 111 Eighth Avenue, the former Port Authority building and one of the most important "telecom carrier hotels" on the East Coast, Google has been working with local officials to help jumpstart New York's tech economy. The search giant is currently donating office space to Cornell University and the Technion-Israel Institute of Technology, which are building a new engineering school on New York's Roosevelt Island. City officials hope the new school will become a locus of research and entrepreneurship to help boost the local economy, much as Stanford has done in Silicon Valley and M.I.T. in Boston.
Google's announcement came on the same day as the release of technology scholar Susan Crawford's important new book, Captive Audience: The Telecom Industry and Monopoly in the New Guilded Age. (And if you think that's a coincidence, I have a bridge to sell you. Susan Crawford is a key member of Mayor Bloomberg's Council on Technology and Innovation.)
In her book, Crawford argues that because U.S. policy makers have allowed a small number of highly profitable corporate giants to dominate the broadband market, Americans have fewer choices for Internet service than millions of other people in developed countries. According to Crawford, broadband Internet access has become an absolutely essential utility for Americans in their education, careers, and personal lives.
(MORE: What Google's FTC Deal Means for the Patent Wars)
Sen. Charles Schumer, the New York Democrat, echoed that sentiment. "Each day access to the Internet becomes more and more important to finding a good job or getting a good education, and this neighborhood-wide wireless network will provide that resource to hundreds of thousands," Schumer said. "This cutting edge wireless network will help to cement New York's reputation as a leader in technological development, will help the city continue to attract business and grow our booming Silicon Alley, and will take us one step closer to our goal of becoming the most well connected city in America."
Of course, Google's motives with the new Chelsea WiFi network are not completely altruistic. Some might even call this a PR stunt. After all, the new WiFi network will only cost $115,000 to build and $45,000 a year to maintain; Google will cover two-thirds of the costs, while nonprofit group Chelsea Improvement Co. will pick up the rest.
Google made $25 billion in profit last year, on $48 billion in revenue, so the PR value of this move is no doubt more valuable to Google than the financial cost. On the other hand, Google benefits when more people use broadband Internet, at faster speeds, because the more Google searches get executed, the more money Google makes.
Google recently launched a plan to provide high-speed fiber-optic Internet access in the Kansas City metropolitan area. The search giant also offers free WiFi in its home city of Mountain View, Calif.
New York City Council Speaker Christine C. Quinn touted the deal as an example of the consumer benefits that can be delivered when private companies work together with local municipalities.
"This public-private partnership benefits the local community while further cementing Google's role as an important contributor to the future development of the area as a hub for the city's technology industry," said Quinn, who is a leading contender to succeed Bloomberg as mayor of New York City.

subset: commoncrawl


text:
Dry Eye And Myopia Management
All parents considering myopia management for their children want to know that the treatments are safe, comfortable and effective. One particular concern is whether myopia treatments could affect their child's dry eye syndrome.
Can a child with dry eye symptoms still be a candidate for each of the myopia management treatments? Is there a chance the myopia treatments could worsen a child's dry eye symptoms? Or perhaps improve them?
There is much to consider, and your optometrist will carefully treat each case on an individual basis.
Below, we'll explain what dry eye syndrome (DES) is and how it may relate to myopia management.
A Brief Overview of Dry Eye Syndrome
DES is a chronic lack of ocular hydration due to insufficient tears or an imbalance in the components that make up the tears (oil, mucus and water).
Certain health conditions, medications, weather conditions, aging, allergies, nutritional deficiencies, and excessive screen time can all contribute to the onset and severity of DES.
Common signs and symptoms of DES include:
- Red, irritated eyes
- Watery eyes
- Stinging or burning eyes
- Grittiness
- Blurred vision
- Light sensitivity
- Stringy mucus around the eyes
- Frequent eye rubbing
DES can be successfully treated in a number of ways, including artificial tears, medicated eye drops, nutritional supplements and by implementing proper eyelid hygiene, like cleaning the eyelids and regions adjacent to the eyes daily. Your eye doctor will prescribe the treatment that targets the underlying cause of your condition.
What Puts Children and Teens at Risk of Developing DES?
Although children have a lower risk of developing DES than adults, they can still suffer from its painful and irritating symptoms. Some experts believe that dry eye syndrome is underdiagnosed in children because they may lack the verbal skills to describe their discomfort.
Risk factors for a child/adolescent developing DES are:
- Allergies
- Certain medications (acne medication, antidepressants, anti-anxiety medications, antihistamines)
- Certain health conditions (blepharitis, herpes simplex viruses, evaporative eye disease, certain neurological disorders, diabetes, inflammatory conditions)
- Excessive screen time (people blink less when staring at a screen
- Nutritional deficiencies
If any of the above factors relate to your child, discuss them with your child's optometrist before deciding on a particular myopia management treatment.
Myopia Management Options and DES
Multifocal Contact Lenses
These lenses are worn during the day and are usually discarded every night. Children naturally produce more oil in their tears and have a higher tear volume, making contact lenses more comfortable to wear and reducing the risk of DES symptoms.
Some research suggests that children with ocular allergies can actually benefit from wearing contact lenses, as the lens creates a barrier between the eye's surface and airborne allergens.
However, children with seasonal allergies who regularly take antihistamines may be prone to DES due to the anticholinergic effects of the medicine that inhibit lacrimal gland functioning and reduce the child's tear volume.
If children experience mild discomfort with daytime lens wear, they may find relief using lubricating eye drops.
Ortho-K Lenses
Ortho-k lenses (also called 'orthokeratology'), are rigid gas-permeable contact lenses that are worn overnight during sleep. These lenses gently and safely change the shape of the cornea, so children don't need to wear glasses or contacts during the day. They are removed in the morning and leave the child with crisp and clear vision.
Ortho-k is a fine choice for children who can't wear daytime lenses due to allergies, DES, or other eye irritations. They are also great for children and teens who participate in sports and other physical activities since no daytime eyewear is required.
Atropine Eye Drops
These medicated eye drops are placed into the eyes once per day and have been shown to effectively slow childhood myopia progression.
Atropine eye drops usually contain preservatives that can cause eye irritation and dryness. However, the low-dose atropine drops prescribed to children have no clinically significant effect on the eyes with regards to DES.
If Your Child Has Myopia, We Can Help!
The bottom line is that even a child with sensitive eyes or DES can still benefit from myopia management treatments. Your optometrist will guide you on what options are the safest, most comfortable and convenient for you and your child.
If your child has myopia or is at risk of developing it, don't wait until it's too late. Halt their myopia now, and they'll thank you later.
To schedule your child's myopia consultation, call Brain Vision Institute today!
Our practice serves patients from Northwest Suburbs of Chicago, South Barrington, Hoffman Estates, and Arlington Heights, Illinois and surrounding communities.


text:
Big Sur California Patch - Highway 1, Coast Hwy 2.5" (Iron on)
Get your hands on this collectible Big Sur California Patch featuring the iconic Highway 1 and Coast Hwy. Measuring 2.5" x 2.5", this patch is perfect for adding to your collection or displaying on your favorite jacket or backpack.
Main Features:
- Iron on patch for easy application
- High quality design and materials
- Collectible item for Big Sur and California enthusiasts
Don't miss out on this must-have Big Sur California Patch. Order yours today!
Application Guidelines for Iron-On Patches:
- Before applying the patch, set your iron to the maximum heat setting (cotton) and allow it to heat up for approximately 3 minutes.
- Test your fabric's heat tolerance at this setting by doing a single pass with the iron on the garment to avoid any damage to the fabric.
- Place the patch on the desired location, then cover it with a cotton cloth or Teflon sheet.
- Using the heated iron, press down firmly on the patch, especially on the edges, and hold for 30 seconds.
- Turn the garment inside-out, then use the heated iron to apply pressure to the back of the patch for another 30 seconds.
- Remove the iron and let the patch cool for approximately 5 minutes.
- For an even more secure hold, it is recommended to sew around the edges of the patch after ironing.
Please note that we cannot guarantee that the patch will adhere to all types of fabric.
Patch Care:
Patches can be washed GENTLY when attached to a garment. When machine washing, it is advisable to turn the garment inside out, secure or close any zippers, hooks, or other items that may snag the patch threads during washing. We recommend washing on the gentle cycle with cold water and allowing it to air dry. It is important to note that ironed-on patches may have loosened adhesive after machine washing. Therefore, we highly recommend sewing the patch or the corners of the patch if you choose to iron it on.
- Choosing a selection results in a full page refresh.
- Opens in a new window.


text:
The Seahawks had three picks in the fourth round of Saturday's final day of the NFL draft, taking with pick No. 108 UCLA DE Cassius March, with pick No. 123 Alabama WR Kevin Norwood and with pick No. 132 Boston College outside linebacker Kevin Pierre-Louis. Here's a quick look at each from CBSSports.com:
Strengths: Displays a quick get-off and pursuit speed. Provides versatility with experience playing along the Bruins' line.h
Weaknesses: Snap anticipation can be a problem. He jumped offsides on consecutive snaps in a key situation against Cal in 2013. A frustrated Marsh was then ejected for throwing a punch.
A versatile defensive lineman, Marsh lined up inside and outside for the UCLA defensive front. At 6-4 and 265 pounds, he has a little bit of a tweener skillset. Playing opposite future top-10 pick Anthony Barr, he has flashed next-level skills. Consistency has been an issue, as well as strength — only 16 reps at 225 pounds at the combine.
Strengths: Flexible body type with adequate height and hand size. Good speed for the position with sharp footwork and leverage in his routes. Quick starter with short-area burst. Smooth body control and excellent mid-air adjustments to twist and look the ball into his hands. Very good concentration and a natural hands-catcher.
Nice awareness to locate, working back to the ball and aggressively attacking it. Never quits on his quarterback. Smart with an alert sideline sense. Knows where the sticks are. Good football character and known as a reliable option on and off the field. Positive attitude and carries himself like a professional. Already has his master's degree.
Weaknesses: Lanky build and average-at-best muscle tone. Needs to get stronger and dedicate himself to the weight room. Tends to play too high and struggles vs. press and physical defenders at the start and peak of routes. Lacks great start/stop explosion and not very creative as a ballcarrier.
Much improved blocker, but still has room to grow in this area. Needs to improve his ball security and be a better finisher. Older prospect and will be a 25-year-old NFL rookie. Below average career production at a school with a talented quarterback and average receivers. Only one career 100-yard receiving game and never led the Tide in receiving.
A three-star WR recruit, Norwood chose Alabama over Mississippi and Southern Mississippi and redshirted in 2009. He was a back-up as a freshman and sophomore, only seeing the field due to a few injuries. With Marquis Maze and Darius Hanks leaving for the NFL, Norwood became a starter as a junior in 2012 and posted consistent production his final two seasons, leading the Tide with seven receiving scores in 2013. He needs to get stronger to better beat press coverage and hold up vs. physical defenders, but he is a mature route runner with excellent hand/eye coordination and reflexes at the catch point.
Norwood isn't a speed demon, but he accelerates well with natural body control. He isn't elite in any one area, but solid across the board. He was somewhat overlooked and underutilized at Alabama, but could end up having a better pro than college career.
KEVIN PIERRE-LOUIS, LB, Boston College, 6-2, 198
Strengths: Athletic movement skills and stays light on his feet. Fluid in his drops with smooth body control. Smart and instinctive with excellent read/react quickness with an explosive first step.
Very active and always around the ball with terrific anticipation. Good eye use to avoid blocks in space while tacking the ballcarrier.
Reliable tackler and stays controlled through the process to finish. Strikes through his target. Aggressively takes on blocks and plays the game as if he were bigger and stronger than he is. Sound ball skills.
Versatile experience, even making impact plays on special teams. Very high football and off-field character with a productive resume as a four-year starter.
Weaknesses: Looks more like a safety with his marginal size and slight body type. Limited strength and growth potential to add much more bulk.
Too easily eliminated by blockers, lacking the power to quickly shed. Flows with the action and loses back-side contain or gets lost in the traffic, struggling to keep himself clean in a crowd. Plays too high and needs to show better bend and pad level to improve his base and technique as a tackler.
Would like to see more of a sense of urgency on every snap. Strong durability concerns with his lack of size and needs to stay healthy for a full season. Missed a handful of games the past few seasons due to injury.


text:
The latest smart home technology is available in Gaston, with Vivint
Enjoy reliable home security, energy savings, and convenience by upgrading your home with a Vivint system. Vivint is the premier smart home provider in North America, serving more than a million customers, and are now extending our award-winning service and high-quality products to the residents of Gaston. When it comes to saving money, the little things add up; unplugging your coffee maker when it's not in use, turning off lights before you leave the room, and adjusting your thermostat to a more economical setting before you walk out the door. Life is busy, and the little things are easy to forget. That's where our revolutionary smart home systems come in. Vivint Smart Drive, our proprietary smart home platform, weaves together all of your devices into an interconnected web and gathers information about your routines and habits and then automatically adjusts to accommodate your lifestyle. Vivint Smart Drive can be controlled through three different channels:
- Vivint Smart Hub - A WiFi, cellular, Z-Wave, and 345 MHz touchscreen panel that mounts inside your home, bundles your devices into one network, and connects directly to 24/7 monitoring services.
- Vivint Mobile - The top-rated smart home app on The App Store that gives you access to your Vivint Smart Hub dashboard through your smartphone or tablet.
- Amazon Echo - A voice-activated control hub that will lock doors, adjust temperatures, arm security systems, or play music. Just say the word!


text:
Are you a keyboardist that wants to enroll in a top Ivey, GA Keyboard School?
If you're looking for one of the Best Colleges for Electronic Keyboard Education, you're in the right place. AIMM is an accredited music college that offers various degree and certificate opportunities that are directly related to the current industry. The music you love and listen to every day is exactly what we teach at our Keyboard School.
In a world saturated with free YouTube lessons and tutorials, it is more critical now than ever to stand out from the crowd. Attending an accredited music college, honing your craft, and learning the absolute best keyboard techniques is a major separating factor. Not to mention the music industry connections you'll make and tons of peers open for music collaboration.
AIMM provides each keyboard player with the instructional and immersive music environment necessary to help develop technical and musical talents in order to acquire the skills necessary to land a successful job in the music industry. Trust us, when you can take a passion and turn it into a comfortable income, it is an amazing feeling. Our number one goal at AIMM is helpful as many dedicated musicians turn that dream into a reality as we can.
And we have the lessons, tools, courses, and connections to do it.
Discover how our music college can help benefit your Keyboard Music Career in Ivey, Georgia.
What You Get at AIMM
The Atlanta Institute of Music Media offers unlimited musical resources to take your professional keyboard career to the highest levels possible. This is much more than online tutorials or private keyboard lessons.
Our music industry-leading faculty teach our performance students the skills necessary to become one of today's elite keyboardist or keyboard teachers. At AIMM, you'll find yourself in an immersive, fast-paced music atmosphere where creativity and music instruction are always the main focus.
Your skills are guaranteed to blossom.
Whether you are looking for:
· Keyboard Lessons
· Keyboard Performance
· Keyboard Techniques
· Piano Lessons and Instruction
· Increased playing speed
· The Number System
· Scales
· Countless Performance and Career Opportunities
· Music Theory and Music Production Education
You will find everything you need to advance your music career at AIMM!
Professional Keyboard Development
AIMM develops our keyboard performance students into successful musicians and teachers.
If you've searched for keyboard lessons near me, tried the Free YouTube content approach, and are still not seeing the growth and results you want - you're not alone. In fact, it's becoming harder and harder to find quality free content online. And that's not even considering the music business side of the industry.
At the Atlanta Institute of Music and Media, we address all industry challenges with hands-on instruction, performance workshops, and music theory and business lessons. Our professional instructors provide keyboard students with the instructional environment necessary to achieve their individualized musical goals.
Their knowledgeable backgrounds allow them to shed light on topics you can't learn from books and YouTube videos. Additionally, our experienced faculty maintains a working relationship with some of the most renowned artists of our time.
To be able to combine elevated skill levels with powerful music connections is a massive edge AIMM students have over the competition in Ivey.
We Push Piano Skills to Their Limit
Our top-rated Ivey Keyboard School provides students with the instructional environment necessary to develop their rhythm, speed, feel, technological & musical proficiency, and acquire the expertise necessary to become one of today's elite musicians.
The curriculum is intense, combining classroom experiences with performance opportunities at every level. You'll be in a fast-paced music atmosphere and learning from industry-leading keyboard instructors. It's a musician's dream - every focus of every minute at AIMM is purely music.
Within each specifically designed program, we challenge our students to become enlightened artists, who are successfully capable of making their own artistic and professional decisions while still working as a member of a larger team.
The keyboard curriculum accomplishes this through:
· Audio and Video Computer Lab Instruction
· Classical and Modern Instruction
· Hands-on Keyboard Lessons and Courses
· Live clinics and workshops featuring today's most well-known and innovative performers, producers, and music industry professionals
AIMM's Ivey Keyboard Programs - Much More Than Keyboard Lessons
AIMM has two immersive and hands-on programs for keyboardists:
· Music and Technology Associate Degree: Keyboard Concentration
· Keyboard Performance Certificate
Let's talk about each music program a little more.
Music and Technology Associate Degree: Keyboard Concentration
The Music and Technology Associate Degree: Keyboard Concentration is the perfect Electronic Keyboard Degree for musicians that want to master the piano, learn the best techniques, fully comprehend music theory and scales, increase performance speed, get their foot in the door of the music industry, and learn beneficial music production techniques.
AIMM is one of the only Ivey Music Colleges the blends instrumentation with music production instruction. As an AVID Pro Tools Training Partner, AIMM offers all of the insider techniques and professional approaches when it comes to recording, mixing, and mastering. For pianists, music production goes hand in hand with the keyboard. This is the perfect opportunity to capitalize on your skill!
Each graduate from AIMM is properly equipped to take on the music industry and create a successful music career.
Keyboard Performance Certificate
Not interested in audio engineering, music production, or sound design? That is okay, too!
We also offer Ivey keyboardists the Keyboard Performance Certificate. This hands-on certificate will help you master your on-stage presence, improvisational abilities, and technical skills.
For musicians that truly want to bolster up their performance skills and are more interested in mastering their stage performance over studio performance, this program has you covered. AIMM's immersive Performance Certificate Program ensures you're always ready and prepared to take every musician around you to the next level.
Also, the certificate is a fairly short program. It can be completed in 12 months, so you'll be back out gigging full-time before you know it.
What Our Keyboard School Offers Prospective Ivey Students
The demand for creative, dynamic, and passionate music professionals is becoming greater than ever, and thanks to advances in music technology, we have the ability to prepare you for a career that can take you anywhere you want to go. With more musicians opting for free online music lessons, the need for technically efficient musicians is on the rise.
We help you rise above the rest.
Below are a few of the many resources and benefits we provide that are necessary for our students to advance their careers.
· Work-Study Program: Students with financial needs have the opportunity to get a part-time position within our campus departments.
· Vast Musical Curriculum Experience: Music students can experience many musical flavors from all different genres including jazz, classical, rock, blues, folk, and R&B. We help you add variety to your musical style.
· Job Placement Upon Graduation: During the final quarter of attendance, our students work with a Placement Specialist to produce a resume and begin exploring in-field employment opportunities.
At AIMM, we are changing the way the world experiences music.
If you're a pianist, want success in the music industry, or are hoping to become a keyboard instructor yourself, then AIMM has the ability, keyboard classes, connections, and opportunities to help you become exactly what you desire to be. We truly believe that no dream is too big to accomplish, and we are here to help every step of the way.
Take the First Step Toward a Successful Piano Career in Ivey
If you want to enroll in the Top Keyboard School near Ivey, there is no better opportunity to separate from the crowd than by enrolling at AIMM.
With the advanced electronic keyboard techniques you learn and the connections you make, you are able to fast-track your career and success within the music industry.
You have the passion. You have the skill level. Now is the time to take action.


text:
Golden South Sea Pearl & Diamond Pendant set in 18k Yellow Gold
- Golden South Sea pearl (13.3mm) and Diamond (DI=0.02ct) Pendant set in matching 18k Yellow Gold.
Product Details
EZcode | 017-00183 |
Metal Type | 18ct Gold |
Metal Colour | Yellow |
Gemstone Type | South Sea Pearl |
Diamond Shape | Round |
Material | Yellow Gold |
Complimentary delivery for all orders over $500. Orders under $500 will be charged a flat fee of $20.
Once your order has shipped, please allow 2-7 business days for delivery depending on your location. Orders requiring ring sizing take up to three (7) additional business days to complete.
If for any reason you are not 100% satisfied with your purchase, you may return it online or in-store within 14 days of delivery for an exchange or store credit. Subject to meeting the requirements.
For more information, visit our FAQ page.
A 12 month guarantee and 30 day change of mind policy applies to online purchases. Why not take advantage of our unique diamond guarantee on manufacture and quality. We're proud of our reputation for providing quality jewellery of the highest calibre. In fact, we're so confident of the quality and workmanship of our jewellery, that every item in range carries our unique Diamond Guarantee. Our guarantee ensures you have selected the finest quality and value for money, covering any manufacturing faults and is conditional upon us making free inspections every six months over the guarantee period.


text:
Camus Cuin
This luxury lochside cottage promises wildlife from the window and an unforgettable island escape.
The content of many of our web listings is provided by third party operators and not VisitScotland. VisitScotland accepts no responsibility for (1) any error or misrepresentation contained in third party listings, and (2) the contents of any external links within web listings ((1) and (2) together hereinafter referred to as the "Content"). VisitScotland excludes all liability for loss or damage caused by any reliance placed on the Content. The Content is provided for your information only and is not endorsed by VisitScotland.


text:
1 Hour Chimney Repair Clifton, Passaic County, New Jersey
Wood, gas or oil furnaces require a correctly sized flue to perform properly.
READ MOREChimney Repair
The chimney is one of the most taken-for-granted parts of a home. Typically it tends to receive neither the attention nor the concern usually accorded other household service systems. The fact that chimneys may do their job reasonably well, even when abused or neglected, contributes to this atmosphere of indifference. Chimneys are far from the passive black holes that most people assume them to be. They perform several vital functions, and their simple appearance misrepresents their complex construction and performance requirements.
A chimney deteriorated by constant exposure to the weather can be a potential safety hazard.
READ MOREFireplace Repair
Thermocrete is the premier solution for fireplace repair. With our advanced spray technology, several layers of ceramic are sprayed inside each flue. This coating seals all small holes and cracks, strengthens the chimney, and increases efficiency without downsizing the flue significantly. Ceramic Flue Sealant (CFS) is a chimney restoration product designed for all types of masonry chimneys. It is an ideal product for Fireplace, Commercial and Historic Home chimney repairs.
All other methods reduce the size of your flue substantially and a smoky and smelly fireplace is a common result.
READ MOREChimney Liner
A Chimney Liner in a masonry chimney is defined as "A clay, ceramic, or metal conduit installed inside of a chimney, intended to contain the combustion products, direct them to the outside atmosphere, and protect the chimney walls from heat and corrosion." Although building codes vary from one state or locality to another, the installation of Chimney Liner has been recommended since the early part of this century, and indeed most fire codes now mandate liners.
Chimney Liners serve three main functions:
READ MOREChimney Flue
A chimney that looks perfectly fine on the outside can be faulty or even dangerous on the inside! Many chimney flues may appear to be in fine condition on the outside. But inside it could be a completely different situation.
A look at the inside of a chimney flue often shows how corrosive residue has attacked the flue. The original clay liner gets eroded away; pieces of it are even missing. Old chimneys might not even have a liner. Mortar and bricks are loose and falling, and moisture can leek through to the home's interior walls.
READ MOREChimney Inspection
With an annual chimney inspection in New Jersey — and possible sweeping — you can improve fireplace and heating flue performance, and snuff out chimney fire and carbon monoxide concerns. Chimney Inspector will confirm if the chimney liner has the ability to contain the products of combustion (i.e., heat, moisture, creosote, and flue gases)
An annual chimney inspection looks for buildup and blockages, followed by sweeping to remove problems inhibiting performance.
READ MOREChimney Certification
New Jersey Uniform Construction Code (NJUCC), requires CHIMNEY CERTIFICATION aka CHIMNEY VERIFICATION for replacement of fuel fired equipment. For Oil and Gas Conversions & For Oil to Oil and Gas to Gas Replacements: The Homeowner, prior to installing the new Furnace, Boiler or Hot Water Heater, must make sure that Chimney is in safe condition, and that Chimney Certification/Verification is signed and given to the Local Code Enforcement Office.
READ MOREAbout 1 Hour Chimney Repair
1 Hour Chimney is Certified by the Chimney Safety Institute of AmericaAt 1 Hour Chimney we know how difficult it is to find skilled and reliable service technicians who also respect the time and effort you put into the upkeep of your home. We take pride in our work because you take pride in your home!
1 Hour Chimney is Certified by the Chimney Safety Institute of America, Accredited and A+ Rated by BBB of NJ, A rated by Angie's List, 5 Star rated by Google and 5 Star rated by Yelp.
AAA Chimney Corp dba 1 Hour Chimney is a family owned company since 1948. Since 2003 the company owners are Tony and Juliette Sapun.


text:
New York, AP—Apple says it received between 4,000 and 5,000 requests from US law enforcement for customer data for the six months ended in May.
The company, like some other businesses, had asked the US government to be able to share how many requests it received related to national security and how it handled them. Those requests were made as part of Prism, the recently revealed highly classified National Security Agency program that seizes records from Internet companies.
Prism appears to do what its name suggests. Like a triangular piece of glass, Prism takes large beams of data and helps the government find discrete, manageable strands of information.
Prism was revealed this month by The Washington Post and Guardian newspapers, and has touched off the latest round in a decade-long debate over what limits to impose on government eavesdropping, which the Obama administration says is essential to keep the nation safe.
Apple Inc. said that between 9,000 and 10,000 accounts or devices were specified in data requests between Dec. 1, 2012, and May 31 from federal, state and local authorities and included both criminal investigations and national security matters.
It said that the most common form of request came from police investigating robberies and other crimes, searching for missing children, trying to locate a patient with Alzheimer's disease, or hoping to prevent a suicide.
The company also made clear how much access the government has.
"We do not provide any government agency with direct access to our servers, and any government agency requesting customer content must get a court order," Apple said in a statement on its website.
Apple explained that its legal team evaluates each request and that it delivers "the narrowest possible set of information to the authorities" when deemed appropriate. The company said that it has refused some requests in the past.
Facebook Inc. has said that it received between 9,000 and 10,000 requests for data from all government agencies in the second half of last year. The social media company said fewer than 19,000 users were targeted.
Apple's stock rose USD 2.12 to USD 432.17 in morning trading on Monday. They have traded in a range of USD 385.10 to USD 705.07 over the past 52 weeks.


text:
Workforce Management Analyst | Cebu
Aces Call Center Jobs Inc.
- Cebu City, PhilippinesPhilippines, Cebu, Cebu CityCebu CityCebuPhilippinesPhilippines
- ₱26,000.00 - ₱27,000.00 / monthPHP260002700026000MONTH
- Full timeFULL_TIME
Job closed.
Job Description
• Performs real time management analysis and execution of plans.
• Generate reports including variance of operational forecast to plan
• Maintain a detailed record of activities, actions and impacts
• Develop budget and call/contact volume/work forecasts based on current and historical call/work volumes and patterns, handle time, productivity trends/patterns and all future call/work requirements
• Analyze current and future call handling resources, attrition trends, learning curve, shrinkage, productivity factors, desk availability and shift requirements, to develop staffing plan.
Minimum Qualifications
- College graduate
- At least 2 years experience in workforce management performing workforce planning
- Demonstrated ability to create and analyze quality reports
- Advanced knowledge in real time management analysis with strong decision making skills
- Intermediate knowledge in performing root cause analysis.
- Highly proficient in using MS Excel
- Willing to work onsite
Perks and Benefits
- Medical / Health Insurance
- Paid Sick Leave
- Performance Bonus
- Recruitment / Signing Bonus
- Paid Holidays
- Paid Vacation Leave
- Maternity & Paternity Leave
Jobs Summary
- Job Level
- Associate / Supervisor
- Job Category
- Customer Service
- Educational Requirement
- Bachelor's degree graduate
- Recruiter response to application
- Always
- Office Address
- Cebu City, Central Visayas, Philippines
About Aces Call Center Jobs Inc.
ACES CALL CENTER JOBS INC. offers jobseekers, with or without experience, the opportunity to work in top BPO and Call Centers in the Philippines in the shortest time possible.
(e.g,, Globe
Prepaid Load Card)
Why Join Us?
CONVENIENCE One Stop Shop - One Day Hiring
Get Hired in One (1) day. Don't waste hours going to different call centers and waiting a few more hours in long lines only to find out that you are not qualified or the job you are interested is not available. After you arrive in ACES CALL CENTER JOBS, you will be processed within 30 minutes and know your possible options on where you are qualified.
Since 2011, over 10,000+ jobseekers found their job through ACES!
CHOICES Comprehensive Active Jobs
Choose from the 20+ Top Call Centers, 150+ locations, 800+ positions, 10,000+ vacancies. There is a perfect job for you in ACES. In ACES, we only endorse you to clients that you have the highest chance of getting hired. Come during our ACES Days and get Hired On The Spot (HOTS)
Since 2011, ACES has consistently been awarded as the Top 3 Recruitment Partner of choice of the Biggest BPOs and Call Centers.
CHARGES It is FREE to apply and ACES gives you 3,000.00 Gift Reward to qualified hires.
It is FREE to apply with us. ACES Call Center Jobs is the only company in the Philippines that gives an extra Php 3,000.00 Gift Reward to its successful hires. This is on top of the incentives that you get from the call centers and is given by ACES.
Since 2011, ACES has given over 30,000,000.00 (Thirty million) worth of Gift Rewards to thousands of jobseekers hired through ACES.
Work at your preferred site! Our clients from Top Multinational companies need more than 200 agents to work in various areas within:
• Makati City
• Ortigas Center
• Mandaluyong City
• Pasig City
• Masinag, Antipolo
• Taguig City - Fort Bonifacio
• Quezon City - Cubao, Eastwood, Commonwealth, Fairview, North EDSA
• South Luzon Area - Sucat, Alabang, Laguna
• Cebu, Iloilo, Pampanga, Baguio, Davao, Cagayan de Oro
• Other Areas
Start as a Customer Service Representative CSR, Technical Support Representative TSR or Choose from the following CALL CENTER AGENT positions:
• Inbound and Outbound Customer Service Reps (CSR)
• Hotel Reservations and Sales or Online Hotel Booking Agents
• Technical Support Representatives (TSR) for various industries
• IT Helpdesk Officers
• Insurance Account Services
• Financial Services - Banking, Fraud, Mortgage, FinTech
• Collections Account - Collection Officers, Medical collection
• Multilingual or Bilingual (English, Japanese, Bahasa, Japanese, Mandarin, Cantonese, Thai, Spanish, French and other Bilingual) - Salary can be as high as 120,000 pesos
• Billing Account Services
• Travel Booking / Airline Ticketing Account
• Pioneer Account / Local accounts
• BPO jobs in the Philippines in Sales, Finance, Customer Service, CSR, TSR, technical support, Healthcare, Insurance, Telco, Banking and thousands of other vacancies
By submitting your application, you agree for Aces Call Center Jobs Inc. to collect and process your personal information for your job application with ACES and its clients in accordance with ACES's Data Privacy Policy contained in this link: https://acesjobs.com.ph/data-privacy.


text:
Whether you are employed or in business, you may find yourself in a financial crisis that requires immediate action. If you are the type of person who does not like borrowing money from friends or family, the crisis may take a toll on you. It is always important to save for such emergencies so that you don't have to borrow. However, borrowing is inevitable. There are two major types of financial lending; long-term and short-term. Long-term financing is a type of financing for buying assets or properties of high value. Short-term borrowing is for meeting immediate or emergency needs and should be repaid within a short period.
Pasadena in Texas TX has several short-term and long-term financing options for its residents and visitors. One of the short-term financing options available in the state is online payday loans Pasadena. A payday loan is an instant short-term unsecured credit that can help you to cover an emergency as you await your paycheck of traditional bank loans. These loans are typically processed within the shortest time possible, usually the same day. This type of financing is becoming increasingly popular throughout Pasadena and other states where it is legal. Borrowers can make a quick online application or walk to a nearby store and make their loan applications.
The requirements for payday loans Pasadena may differ in other states or countries like the UK. However, because the loans are designed for customers to borrow and repay within a short period, lenders usually charge a higher interest rate than the traditional bank loans. Pasadena in Texas has laws to protect payday loan borrowers from lenders who may want to exploit them. These laws are outlined in Pasadena Code Ann. 45-17-101 et seq.
If you live in Pasadena or planning to relocate to the state, one of your considerations is whether you can get quick financing during emergencies. Although online payday loans Pasadena in Texas TX is popular across the state, not all people know what it is or how to apply for the credit from direct lenders. Some people cannot understand what signs with captions "Get Money Now" or "No Credit Check" means. If you are such a person, worry no more. This article highlights all you need to know about Pasadena payday loans online and how you can qualify for it.
Pasadena payday loans, also known as Pasadena payday cash advances, are small short-term unsecured loans that are available for Pasadena residents. Payday lending is also known as cash advance loan, small-dollar loan, or payroll loan. The term "payday" means that the next paycheck should repay the loan. That is, your lender agrees to give you a sum of money, which he will recover from your next payday salary. However, a payday loan is not only for salaried people but also for people with steady income sources.
One of the popular questions you may ask any direct lender is: how much payday loan do I qualify for? The amount of credit that you are eligible for depends on your payslip and the maximum amount that lenders are allowed by law to disburse. In Pasadena of Texas, you can legally borrow a maximum of $500 if you apply in-store and $425 if you apply online. However, your next payday salary should be equal to the borrowed amount plus interest fee or more. No lender will finance you more than your next income. However, you only need to borrow the amount that you need. No matter the amount you borrow, the law requires that you repay within 31 days. Also, the lender should charge interest of no more than 15% of the amount borrowed.
Not everybody in Pasadena qualifies for a payday loan. The loan is restricted to protect both lenders and borrowers. If you live in Pasadena, it would be wise for you to confirm whether you meet the following requirement before heading online to make your application.
Payday loans Pasadena no credit check are strictly for US citizens who are also permanent residents of the state. Permanent residency means that you live and work in Pasadena and not necessarily born there. Therefore, you can not apply for the payday loan if you are a resident of another state, even if you are visiting Pasadena.
Now that you are a permanent resident of Pasadena, the next huddle you must pass is the age limit. Most state laws allow only people who are at least 18 years old or adults to access any financing. Pasadena is one of those states that are strict on who can access not only payday loans but also other forms of funding. Therefore, when making an application for payday advance loans Pasadena TX, your lender will require you to provide a personal identification document.
Because payday loans are pegged on the next payday salary or paycheck, you must have a steady income source. You must either have a salary or business where direct lenders can recover the sum lent to you. A constant source of income also increases your creditworthiness.
If you are applying for a pay day loan Pasadena in Texas TX, you must provide a checking account. This is the account where lenders can transfer the cash if your application is approved. A checking account must bear your details and active. However, if you opt for payday loans Pasadena no checking account application, you will simply walk into an in-store, make your application, and wait for the paycheck.
Some lenders may also want to check your credit rating to determine your creditworthiness and repayment ability. Bad credit rating means that you are likely to default or delay payment, while a good rating gives the lender confidence to approve your application quickly. However, some lenders don't consider credit rating when appraising your application since the loan is pegged on the next paycheck.
When you have a financial emergency, you always think of immediate need. However, emergencies are unpredictable, and you cannot prepare adequately for them. You can repair a car today and break down again tomorrow. So, you need a constant source of cash to manage emergencies. If you previously borrowed 24 hour payday loans Pasadena in Texas, you still can borrow the loan as long as your next payday salary can support the repayment up to a maximum amount of $500. However, the state law allows you to borrow up to a maximum of three times before any repayment. It is prudent to borrow only the amount you need for your first borrowing to leave room for additional financing. Some states allow you to borrow only once and repay before you can borrow again.
The good thing about multiple payday loans Pasadena is that lenders do not charge any extra fee. They will only charge an interest rate of 15% for the amount that you borrow. For instance, if you borrow $100 today and another $100 next week, you will pay a $15 interest fee for the first borrowing and another $15 for the second borrowing. You will have paid $30 in interest in total, which is 15% of the total amount borrowed.
Whether you borrow payday loans Pasadena once or multiple times but pay the whole amount before their due dates, the lender cannot charge you an additional prepayment fee. The amount of interest will also not reduce. You still have to pay the 15% interest rate. If you default the loans for whatever reason, the law does not allow the payday lender to charge a fee for collecting the defaulted or unpaid bill.
When you apply for a payday loan in Pasadena, you hope that the application will go through. However, sometimes you may wait for positive feedback, which is a credit to your checking account, only for you denied the credit. There are several reasons why direct lenders can deny you a payday loan. Here are some of these reasons;
When you make your payday loans Pasadena no credit check application online or offline, the lender will scan through the application form to check if you meet the lending requirements. If you are not a Pasadena resident, do not have a steady income source, or are under 18 years, you will not get the credit.
When you are filling the online application form, you need to provide accurate information. Also, you need to fill all the required spaces. If you leave blank spaces on the form or provide inaccurate information, it may raise a red of concern or lead to the lender rejecting your application.
A checking account enables the lender to transfer the money after approving your loan application. If you provide a dormant account or an incorrect checking account, the lender cannot move the funds. Thus, he/she will cancel your application or ask you to provide another checking account.
A steady source of income guarantees that you will repay the payday loan within the agreed time. It is also one of the factors that may affect your creditworthiness and determine the amount you will get as a payday loan. If you do not have a steady income source, the lender will not risk giving you credit.
A credit rating is a measure of your repayment ability as well as your creditworthiness. Several factors can contribute to bad credit rating, including bad credit history, multiple borrowing, and defaulting on loans. A bad credit rating shows that you are likely to default or not repay the loan. So, lenders will not want to risk giving payday loans if you are likely not to repay.
Pasadena law allows you to borrow three times to a maximum of $500. Thus, you cannot borrow more than three times or over $500. Lenders will automatically reject your loan application if you the amount you have applied for exceed the maximum amount or have previously borrowed three times. That is why you should apply for small amounts for multiple borrowing.
When you qualify for a payday loan, the feeling of knowing that you will sort out your emergency needs can be out of this world. As you celebrate the success of your application, you need to remember that you have you will have to repay the whole amount within the repayment period. Paying off the credit is as easy as applying for it. However, if you do not plan well for the repayment, you may get deeper into debt, which may ruin your credit rating.
Before you apply for the payday loan, you need to create a realistic personal budget, including your financial obligations and expenses. Having a budget will help you know what you can pay back so that you do not borrow what you will have difficulty repaying. Once you have figured out the amount that you can pay, you can go ahead and apply for the loan.
There are several ways to pay off your 24 hour payday loans Pasadena in Texas. However, the repayment method may depend on what is favorable for your lender. In most cases, lenders require that you write them a postdated check, which includes the amount borrowed and the interest. They will then cash the check on the agreed date and pay off the loan. Some lenders prefer that you establish a one-time standing order from your account to theirs so that the funds can be transferred automatically when your employer credits your account.
You can also deposit cash directly to the lender's account and then present a deposit slip or receipt. The bottom line is that most lenders do not mind how you repay the loan as long as you do not default.
Unfortunately, you may not be in a position to repay the loan for genuine reasons. In this case, you should know what to do.
Final thoughts
Online payday loans Pasadena in Texas TX will come in handy for people with emergency financial needs. Although payday loans are available for Pasadena residents, they must meet specific criteria to access it. Lending firms should ensure that they give loans only to people who meet these criteria to reduce the number of people defaulting.
Applying does NOT affect your credit score!
No credit check to apply.