Dmitry M Kakurin

US Patent:

20040172474, Sep 2, 2004

Filed:

Aug 15, 2003

Appl. No.:

10/641525

Inventors:

Mark Markaryan - Seattle WA, US
Dmitry Kakurin - Redmond WA, US
Sean Olson - Kirkland WA, US
Srikanth Shoroff - Sammamish WA, US
Radu Ionescu - Redmond WA, US

Assignee:

Microsoft Corporation - Redmond WA

International Classification:

G06F015/16

US Classification:

709/228000, 709/246000

Abstract:

The present invention allows a server to delay allocating resources to a client's request. When the client requests a feature that requires server resources, the server accepts and acknowledges the client's request, but the client is prohibited from using the requested feature until further notice from the server. For example, during an authorization process, the server allocates only the minimum resources required to maintain the session and to authorize the client. Thereafter, the server allocates the resources necessary to support the client's request only when the resources become available. Until then, the server maintains the communications session without supporting the request. Thus, the server shepherds its resources rather than committing them at the whim of a client. Also, a client need not repeat its request if the server cannot immediately satisfy it; instead, the server accepts the request and then later begins to support it when adequate resources become available.

US Patent:

20120079014, Mar 29, 2012

Filed:

Dec 1, 2011

Appl. No.:

13/309331

Inventors:

Mark Markaryan - Seattle WA, US
Dmitry M. Kakurin - Redmond WA, US
Sean C. Olson - Kirkland WA, US
Srikanth Shoroff - Sammamish WA, US
Radu Ionescu - Redmond WA, US

Assignee:

Microsoft Corporation - Redmond WA

International Classification:

G06F 15/16

US Classification:

709203

Abstract:

The present invention allows a server to delay allocating resources to a client's request. When the client requests a feature that requires server resources, the server accepts and acknowledges the client's request, but the client is prohibited from using the requested feature until further notice from the server. For example, during an authorization process, the server allocates only the minimum resources required to maintain the session and to authorize the client. Thereafter, the server allocates the resources necessary to support the client's request only when the resources become available. Until then, the server maintains the communications session without supporting the request. Thus, the server shepherds its resources rather than committing them at the whim of a client. Also, a client need not repeat its request if the server cannot immediately satisfy it; instead, the server accepts the request and then later begins to support it when adequate resources become available.

US Patent:

20140195632, Jul 10, 2014

Filed:

Jan 4, 2013

Appl. No.:

13/734769

Inventors:

- Redmond WA, US
Jinsong Yu - Bellevue WA, US
Martin Taillefer - Redmond WA, US
Gregory Michael Neverov - Seattle WA, US
Dmitry Kakurin - Redmond WA, US
Ahmed Hassan Mohamed - Redmond WA, US
John J. Duffy - Seattle WA, US
Christopher Wellington Brumme - Mercer Island WA, US
F. Soner Terek - Bellevue WA, US

Assignee:

MICROSOFT CORPORATION - Redmond WA

International Classification:

G06F 15/167

US Classification:

709213

Abstract:

The environment and use of an immutable buffer. A computing entity acquires data or generates data and populates the data into the buffer, after which the buffer is classified as immutable. The classification protects the data populated within the immutable buffer from changing during the lifetime of the immutable buffer, and also protects the immutable buffer from having its physical address changed during the lifetime of the immutable buffer. As different computing entities consume data from the immutable buffer, they do so through views provided by a view providing entity. The immutable buffer architecture may also be used for streaming data in which each component of the streaming data uses an immutable buffer. Accordingly, different computing entities may view the immutable data differently without having to actually copy the data.