Abstract: A computing system includes a processor and a data store coupled to the processor. The computing system provides access to electronic content stored in the data store. A user interface component receives an indication of an external user with which to share an item of electronic content. A link generation component is generates a link to share the item of electronic content. An access control component receives a request from a requestor to access the item of electronic content using the link, and responsively verify an identity of a requestor. The user interface component provides access to the item of electronic content to the requestor if the identity was verified and receives a user input indicative of an external account binding request. The access control component determines if the requestor has authenticated with the external account and selectively binds the link to the external account if the user authenticates with the external account.

Abstract: A computing system includes a processor and memory storing instructions executable by the at least one processor. The instructions, when executed, provide a user interface component that receives an indication of an external user with which to share an item of electronic content, a link generation component that generates a link to share the item of electronic content and identifies a communication endpoint associated with the external user, and an access control component that receives a request to access the item of electronic content using the link and, in response to the request, generates an access code that is communicated to the communication endpoint associated with the external user. The user interface component receives an access input, and the access control component grants access to the item of electronic content based on a determination that the access input includes the access code communicated to the communication endpoint associated with the external user.

Abstract: A computing system includes a processor and a data store coupled to the processor. The computing system is configured to provide access to electronic content stored in the data store. A user interface component is configured to receive an indication of an external user with which to share an item of electronic content. A link generation component is configured to generate a link to share the item of electronic content. An access control component is configured to receive a request to access the item of electronic content using the link, and responsively generate an access code that is communicated to a known endpoint associated with the link. The user interface component is configured to receive a user input containing a user-entered access input. The access control component is configured to selectively grant access to the item of electronic content based on whether the user-entered access input matched the access code communicated to the known endpoint associated with the link.

Abstract: A computing system includes a processor and a data store coupled to the processor. The computing system is configured to provide access to electronic content stored in the data store. A user interface component is configured to receive an indication of an external user with which to share an item of electronic content. A link generation component is configured to generate a link to share the item of electronic content. An access control component is configured to receive a request from a requestor to access the item of electronic content using the link, and responsively verify an identity of a requestor. The user interface component is configured to provide access to the item of electronic content to the requestor if the identity was verified and receive a user input indicative of an external account binding request.

Abstract: Techniques are described to incrementally change the availability of a feature of a software service to clients over a network based on a configuration setting indicating the proportion of the clients that is eligible to receive the feature. In an implementation, a client rank is generated for a client on the network based on a client identification that identifies the client and a feature identification that identifies the feature. The feature may then be made available to the clients via the network if a comparison of the client rank with the configuration setting indicates that the client is eligible to access the feature.

Abstract: Techniques are described to incrementally change the availability of a feature of a software service to clients over a network based on a configuration setting indicating the proportion of the clients that is eligible to receive the feature. In an implementation, a client rank is generated for a client on the network based on a client identification that identifies the client and a feature identification that identifies the feature. The feature may then be made available to the clients via the network if a comparison of the client rank with the configuration setting indicates that the client is eligible to access the feature.

Abstract: Techniques are described to incrementally change the availability of a feature of a software service to clients over a network based on a configuration setting indicating the proportion of the clients that is eligible to receive the feature. In an implementation, a client rank is generated for a client on the network based on a client identification that identifies the client and a feature identification that identifies the feature. The feature may then be made available to the clients via the network if a comparison of the client rank with the configuration setting indicates that the client is eligible to access the feature.

Abstract: Techniques are described to deliver client content on a webpage. In implementations, client content is retrieved to be presented in a webpage to be served to a client. A presentation template is also retrieved. The presentation template includes at least one server-side tag configured to define a presentation of the client content in the webpage. The client content is then integrated with the presentation template by the server as defined by the at least one tag to generate the webpage.

Abstract: Aspects of the subject matter described herein relate to creating, maintaining, and using relationships between items. In aspects, items such as files, folders, and other objects may be stored in a data store. A user may desire to form a relationship between two items that provides additional semantic information regarding the relationship. To do so, an instance of an item reference is created and populated with data that associates the item reference with a source item and optionally a target item. The item reference is part of a type hierarchy and inherits properties from ancestor types. These types are included in a payload of the item reference and may be exposed to programs that seek to obtain information about the relationship indicated by the item reference. An item reference may be added without changing other data about the referenced items.

Abstract: Techniques are described to incrementally change the availability of a feature of a software service to clients over a network based on a configuration setting indicating the proportion of the clients that is eligible to receive the feature. In an implementation, a client rank is generated for a client on the network based on a client identification that identifies the client and a feature identification that identifies the feature. The feature may then be made available to the clients via the network if a comparison of the client rank with the configuration setting indicates that the client is eligible to access the feature.

Abstract: Systems, methods, and computer program products for deleting objects from device stores without deleting corresponding objects from one or more synchronization partners. A device has a device sync module for each synchronization partner and each device sync module maintains tracking data. Alternatively, a single device sync module manages the tracking data of each synchronization partner. When an object does not meet parameters of a synchronization filter, a soft delete request is made to the wireless device. A sync manager receives the soft delete request and determines from the other device sync modules that have registered with the sync manager whether they continue to synchronize the object. If none of the other device sync modules protest, the object is deleted. If one of the device sync modules objects to the delete request, then the delete is denied. The tracking data for all of the device sync modules is appropriately modified.

Abstract: Aspects of the subject matter described herein relate to creating, maintaining, and using relationships between items. In aspects, items such as files, folders, and other objects may be stored in a data store. A user may desire to form a relationship between two items that provides additional semantic information regarding the relationship. To do so, an instance of an item reference is created and populated with data that associates the item reference with a source item and optionally a target item. The item reference is part of a type hierarchy and inherits properties from ancestor types. These types are included in a payload of the item reference and may be exposed to programs that seek to obtain information about the relationship indicated by the item reference. An item reference may be added without changing other data about the referenced items.

Abstract: In one embodiment, a method of parsing an XML data stream comprises receiving an XML data stream containing a namespace prefix and an associated element tag name. The element tag name is associated with an element tag. The namespace prefix and the element tag name are converted into a token that uniquely represents a namespace specification that is associated with the namespace prefix and the element tag. A stack is defined and is configured to receive one or more tokens during parsing of the XML data stream. Parsing of the XML data stream is performed without requiring an XML tree structure comprising an XML document embodied by the XML data stream, to be built.

Abstract: Systems, methods, and computer program products for deleting objects from device stores without deleting corresponding objects from one or more synchronization partners. A device has a device sync module for each synchronization partner and each device sync module maintains tracking data. Alternatively, a single device sync module manages the tracking data of each synchronization partner. When an object does not meet parameters of a synchronization filter, a soft delete request is made to the wireless device. A sync manager receives the soft delete request and determines from the other device sync modules that have registered with the sync manager whether they continue to synchronize the object. If none of the other device sync modules protest, the object is deleted. If one of the device sync modules objects to the delete request, then the delete is denied. The tracking data for all of the device sync modules is appropriately modified.

Abstract: Systems for parsing an XML data stream are described. In one embodiment, the system is configured to receive an XML data stream comprising one or more element tags and determine whether an element tag contains a namespace declaration. The system creates one or more namespace objects if an element tag contains one or more respective namespace declarations, each namespace object corresponding to one namespace declaration. The system associates namespace objects with one another if more than one namespace object is created and associates each namespace object with a dictionary that contains one or more entries that are associated with an element tag.

Abstract: In one embodiment, a method of parsing an XML data stream comprises receiving an XML data stream containing a namespace prefix and an associated element tag name. The element tag name is associated with an element tag. The namespace prefix and the element tag name are converted into a token that uniquely represents a namespace specification that is associated with the namespace prefix and the element tag. A stack is defined and is configured to receive one or more tokens during parsing of the XML data stream. Parsing of the XML data stream is performed without requiring an XML tree structure comprising an XML document embodied by the XML data stream, to be built.

Abstract: Various features enable an XML data stream to be parsed without the need to build a hierarchical tree structure for the XML document. In the described embodiment, the concept of an element or namespace stack is utilized as a way of organizing parsing activities and maintaining a definable place within the structure of the XML document. Various structures work together with the element or namespace stack to facilitate piecewise parsing of the XML data stream. One structure is a namespace hierarchy that is a collection of namespace objects that each represent a namespace specification that is encountered in the XML data stream. Each object includes a namespace prefix and an associated namespace specification. This structure creates a hierarchical organization that is used for mapping a particular encountered namespace specification into a unique value that represents both the namespace specification and an element tag in which the namespace specification occurs.

Abstract: Various features enable an XML data stream to be parsed without the need to build a hierarchical tree structure for the XML document. In the described embodiment, the concept of an element or namespace stack is utilized as a way of organizing parsing activities and maintaining a definable place within the structure of the XML document. Various structures work together with the element or namespace stack to facilitate piecewise parsing of the XML data stream. One structure is a namespace hierarchy that is a collection of namespace objects that each represent a namespace specification that is encountered in the XML data stream. Each object includes a namespace prefix and an associated namespace specification. This structure creates a hierarchical organization that is used for mapping a particular encountered namespace specification into a unique value that represents both the namespace specification and an element tag in which the namespace specification occurs.

Abstract: Systems, methods, and computer program products for deleting objects from device stores without deleting corresponding objects from one or more synchronization partners, A device has a device sync module for each synchronization partner and each device sync module maintains tracking data. Alternatively, a single device sync module manages the tracking data of each synchronization partner. When an object does not meet parameters of a synchronization filter, a soft delete request is made to the wireless device. A sync manager receives the soft delete request and determines from the other device sync modules that have registered with the sync manager whether they continue to synchronize the object. If none of the other device sync modules protest, the object is deleted. If one of the device sync modules objects to the delete request, then the delete is denied. The tracking data for all of the device sync modules is appropriately modified.