Microsoft Technology Licensing, LLC

A Perry Clarke

Keith Stuart Kaplan

Aaron Hartwell

Ronald Eric Gray

Nicole A Bonilla

Daniel Edward Lovinger

Alec C Dun

Steven F Goddard

Joseph K W Chan

Xiaowen Shan

Dale Koetke

Michael C Price

Marc R Allen

Neil R Kaethler

L Felipe Cabrera

The performance of client server interactions is measured by the interacting client. The client-generated performance data is efficiently transmitted to one or more servers by incorporating the performance data regarding one or more previous request/response cycles into a subsequent request. Performance data transmission is made more efficient by transmitting performance data context such as client, server and session details once per connection. Performance data is stored on the client until transmitted or until it has aged beyond a server specified maximum age. Performance data is aggregated on the server in memory resident accumulators. The server may have a set of accumulators for each server its clients communicate with as well as a set for each client. An accumulator value crossing a configurable threshold may trigger an event log entry. The number of performance data events in an event class may be limited to a maximum for a time period.

System and method for client side monitoring of client server communications

A mechanism is provided that allows an application program to write, as a single file, a large block of data comprising multiple portions that could otherwise be written as several smaller files, then to access, as individual files, each of the portions within the large block of data, and to be able to create individual files efficiently out of each of these subfiles. The mechanism may be partially embodied in a file system that includes an information store defining each file on a volume. The application program writes, via the file system, a single file to the volume as (preferably) a contiguous block of data. The single file includes two or more separable streams of data capable of being stored as individual files (subfiles). Once the single file is written to the volume, multiple entries are made to the information store. Each entry defines and points to a subfile within the single file. The subfiles may be positioned within the single file such that the beginning of each subfile lies on the beginning of an allocation unit. In this manner, the single file may be written to the volume in one efficient operation, yet each subfile is individually accessible via its respective entry in the information store.

System and method for creating multiple files from a single source file

Growing community of inventors

Bellevue, WA, United States of America

A Perry Clarke