David F Hartley

US Patent:

6763360, Jul 13, 2004

Filed:

Sep 6, 2001

Appl. No.:

09/947893

Inventors:

David J. Hartley - Bellevue WA

Assignee:

Microsoft Corporation - Redmond WA

International Classification:

G06F 1700

US Classification:

707102, 7071041

Abstract:

Measuring the reliability of a version of a software module in a customized manner that is independent of the written language used by versions of the software module to output objects. Language independent state tables may be generated from one version of a software module and then used to facilitate measuring the reliability of other versions of the software module. During the testing process, standardized pointers are used to reference objects that are common to a plurality of versions of a software module. Parameters representative of an actual state of a software module are compared to parameters representative of an anticipated state of the software module to determine if an action has performed as intended. Customized functions may be automatically loaded during the testing process and may receive data standardized for use with a plurality of version of a software module via common function headers.

US Patent:

7277700, Oct 2, 2007

Filed:

Feb 2, 2006

Appl. No.:

11/347520

Inventors:

Ahmad M. El Husseini - Redmond WA, US
Shawn Kashyap - Bellevue WA, US
David J. Hartley - Bellevue WA, US

Assignee:

Microsoft Corporation - Redmond WA

International Classification:

H04Q 7/20

US Classification:

455423, 455418, 455419, 455420, 455424, 455425, 455 6711, 4551151, 3702411, 370248, 370252, 379 901, 379 1501, 379 1503, 379 2602, 379 2704, 703 24, 703 28, 709224, 709250

Abstract:

A system and method for emulating a telephone driver of a mobile device to assist in the development and testing of mobile telephony applications is described. An emulated telephony driver maintains internal states of a wireless network and characteristics of the mobile device. A wireless network is simulated such that neither a cellular radio nor a mobile subscription are required for handset application development and testing.

US Patent:

20130262862, Oct 3, 2013

Filed:

Mar 30, 2012

Appl. No.:

13/435233

Inventors:

David John HARTLEY - Bellevue WA, US

Assignee:

DECHO CORPORATION - Seattle WA
VMWARE, INC. - Palo Alto CA

International Classification:

H04L 9/08
G06F 17/30

US Classification:

713165

Abstract:

Systems and methods for providing privacy of file synchronization with sharing functionality are presented. In embodiments, a file synchronization system comprises one or more folders associated with one or more non-shared encryption keys, which may be a managed key shared across an organization, and/or a personal key that is not shared or has limited third-party sharing. The one or more non-shared encryption keys are not known to the data storage service. The file synchronization system may also contain one or more folders associated with a shared encryption key that is shared with the data storage service, and in embodiments, with a set of users of the service. The system may include a mapping correlating folders to encryption type so items in each folder can be handled appropriately. The system may have additional folders, such as one or more public folders that may be available with limited or no restrictions.

US Patent:

D361558, Feb 20, 1990

Filed:

Aug 29, 1988

Appl. No.:

7/238573

Inventors:

John P. Stahler - La Jolla CA
David B. Hartley - San Diego CA
Stephen O. Ross - Del Mar CA

Assignee:

Robot Research, Inc. - San Diego CA

US Classification:

D13 35

US Patent:

20140208124, Jul 24, 2014

Filed:

Mar 24, 2014

Appl. No.:

14/223888

Inventors:

- Seattle WA, US
- Palo Alto CA, US
David John HARTLEY - Bellevue WA, US

Assignee:

DECHO CORPORATION - Seattle WA
VMWARE, INC. - Palo Alto CA

International Classification:

G06F 21/60

US Classification:

713189

Abstract:

Systems and methods for providing privacy of file synchronization with sharing functionality are presented. In embodiments, a file synchronization system comprises one or more folders associated with one or more non-shared encryption keys, which may be a managed key shared across an organization, and/or a personal key that is not shared or has limited third-party sharing. The one or more non-shared encryption keys are not known to the data storage service. The file synchronization system may also include one or more folders associated with a shared encryption key that is shared with the data storage service, and in embodiments, with a set of users of the service. The system may include a mapping correlating folders to encryption type so items in each folder can be handled appropriately. The system may have additional folders, such as one or more public folders that may be available with limited or no restrictions.