Patents by Inventor Daniel Willhite
Daniel Willhite has filed for patents to protect the following inventions. This listing includes patent applications that are pending as well as patents that have already been granted by the United States Patent and Trademark Office (USPTO).
-
Patent number: 8667508Abstract: A method for providing stand-in objects, where relationships among objects are automatically resolved in an object oriented relational database model without the necessity of retrieving data from the database until it is needed. A “fault” class is defined, as well as fault objects whose data haven't yet been fetched from the database. An object that's created for the destination of a relationship whenever an object that includes the relationship is fetched from the database. When an object is fetched that has relationships, fault objects are created to “stand-in” for the destination objects of those relationships. Fault objects transform themselves into the actual enterprise objects—and fetch their data—the first time they're accessed. Subsequently, messages sent to the target objects are responded to by the objects themselves.Type: GrantFiled: May 2, 2012Date of Patent: March 4, 2014Assignee: Next Software, Inc.Inventors: Richard Williamson, Linus Upson, Daniel Willhite, Jack Greenfield
-
Publication number: 20120246664Abstract: A method for providing stand-in objects, where relationships among objects are automatically resolved in an object oriented relational database model without the necessity of retrieving data from the database until it is needed. A “fault” class is defined, as well as fault objects whose data haven't yet been fetched from the database. An object that's created for the destination of a relationship whenever an object that includes the relationship is fetched from the database. When an object is fetched that has relationships, fault objects are created to “stand-in” for the destination objects of those relationships. Fault objects transform themselves into the actual enterprise objects—and fetch their data—the first time they're accessed. Subsequently, messages sent to the target objects are responded to by the objects themselves.Type: ApplicationFiled: May 2, 2012Publication date: September 27, 2012Applicant: NeXT Software, Inc.Inventors: Richard Williamson, Linus Upson, Daniel Willhite, Jack Greenfield
-
Publication number: 20110246536Abstract: The present invention creates a model that maps object classes in an object-oriented environment to a data source. The model maps the relationship between properties of each object class and data of the data source. The present invention can be used with a data source such as a relational database, user interface, file system, or object-oriented database. An application's object classes and data source schema are designed independent of the other since the model can be used to map one to the other. The model is comprised of entities and attributes. An entity maps to an object class and to at least one table of the DBMS. An entity contains attributes either simple or derived. A simple attribute maps to a DBMS column. A derived attribute is a combination of other attributes and does not directly map to a DBMS column. A relationship creates a link between entities of the model. A relationship can be used to flatten an attribute or flatten a relationship.Type: ApplicationFiled: June 10, 2011Publication date: October 6, 2011Applicant: NEXT SOFTWARE, INC.Inventors: Richard Williamson, Linus Upson, Jack Greenfield, Daniel Willhite
-
Patent number: 7984017Abstract: The present invention creates a model that maps object classes in an object-oriented environment to a data source. The model maps the relationship between properties of each object class and data of the data source. The present invention can be used with a data source such as a relational database, user interface, file system, or object-oriented database. An application's object classes and data source schema are designed independent of the other since the model can be used to map one to the other. The model is comprised of entities and attributes. An entity maps to an object class and to at least one table of the DBMS. An entity contains attributes either simple or derived. A simple attribute maps to a DBMS column. A derived attribute is a combination of other attributes and does not directly map to a DBMS column. A relationship creates a link between entities of the model. A relationship can be used to flatten an attribute or flatten a relationship.Type: GrantFiled: July 31, 2006Date of Patent: July 19, 2011Assignee: Next Software, Inc.Inventors: Richard Williamson, Linus Upson, Jack Greenfield, Daniel Willhite
-
Publication number: 20090187921Abstract: A method for providing stand-in objects, where relationships among objects are automatically resolved in an object oriented relational database model without the necessity of retrieving data from the database until it is needed. A “fault” class is defined, as well as fault objects whose data haven t yet been fetched from the database. An object that's created for the destination of a relationship whenever an object that includes the relationship is fetched from the database. When an object is fetched that has relationships, fault objects are created to “stand-in” for the destination objects of those relationships. Fault objects transform themselves into the actual enterprise objects—and fetch their data—the first time they're accessed. Subsequently, messages sent to the target objects are responded to by the objects themselves.Type: ApplicationFiled: March 30, 2009Publication date: July 23, 2009Applicant: NEXT SOFTWARE, INC.Inventors: Richard Williamson, Linus Upson, Daniel Willhite, Jack Greenfield
-
Patent number: 7539997Abstract: A method for providing stand-in objects, where relationships among objects are automatically resolved in an object oriented relational database model without the necessity of retrieving data from the database until it is needed. A “fault” class is defined, as well as fault objects whose data haven't yet been fetched from the database. An object that's created for the destination of a relationship whenever an object that includes the relationship is fetched from the database. When an object is fetched that has relationships, fault objects are created to “stand-in” for the destination objects of those relationships. Fault objects transform themselves into the actual enterprise objects—and fetch their data—the first time they're accessed. Subsequently, messages sent to the target objects are responded to by the objects themselves.Type: GrantFiled: July 31, 2006Date of Patent: May 26, 2009Assignee: Next Software, Inc.Inventors: Richard Williamson, Linus Upson, Daniel Willhite, Jack Greenfield
-
Patent number: 7523458Abstract: A method for providing stand-in objects, where relationships among objects are automatically resolved in an object oriented relational database model without the necessity of retrieving data from the database until it is needed. A “fault” class is defined, as well as fault objects whose data haven't yet been fetched from the database. An object that's created for the destination of a relationship whenever an object that includes the relationship is fetched from the database. When an object is fetched that has relationships, fault objects are created to “stand-in” for the destination objects of those relationships. Fault objects transform themselves into the actual enterprise objects—and fetch their data—the first time they're accessed. Subsequently, messages sent to the target objects are responded to by the objects themselves.Type: GrantFiled: September 23, 2005Date of Patent: April 21, 2009Assignee: Next Software, Inc.Inventors: Richard Williamson, Linus Upson, Daniel Willhite, Jack Greenfield
-
Publication number: 20070094302Abstract: The present invention creates a model that maps object classes in an object-oriented environment to a data source. The model maps the relationship between properties of each object class and data of the data source. The present invention can be used with a data source such as a relational database, user interface, file system, or object-oriented database. An application's object classes and data source schema are designed independent of the other since the model can be used to map one to the other. The model is comprised of entities and attributes. An entity maps to an object class and to at least one table of the DBMS. An entity contains attributes either simple or derived. A simple attribute maps to a DBMS column. A derived attribute is a combination of other attributes and does not directly map to a DBMS column. A relationship creates a link between entities of the model. A relationship can be used to flatten an attribute or flatten a relationship.Type: ApplicationFiled: July 31, 2006Publication date: April 26, 2007Inventors: Richard Williamson, Linus Upson, Jack Greenfield, Daniel Willhite
-
Publication number: 20070039008Abstract: A method for providing stand-in objects, where relationships among objects are automatically resolved in an object oriented relational database model without the necessity of retrieving data from the database until it is needed. A “fault” class is defined, as well as fault objects whose data haven t yet been fetched from the database. An object that's created for the destination of a relationship whenever an object that includes the relationship is fetched from the database. When an object is fetched that has relationships, fault objects are created to “stand-in” for the destination objects of those relationships. Fault objects transform themselves into the actual enterprise objects—and fetch their data—the first time they're accessed. Subsequently, messages sent to the target objects are responded to by the objects themselves.Type: ApplicationFiled: July 31, 2006Publication date: February 15, 2007Inventors: Richard Williamson, Linus Upson, Daniel Willhite, Jack Greenfield
-
Patent number: 7127474Abstract: The present invention creates a model that maps object classes in an object-oriented environment to a data source. The model maps the relationship between properties of each object class and data of the data source. The present invention can be used with a data source such as a relational database, user interface, file system, or object-oriented database. An application's object classes and data source schema are designed independent of the other since the model can be used to map one to the other. The model is comprised of entities and attributes. An entity maps to an object class and to at least one table of the DBMS. An entity contains attributes either simple or derived. A simple attribute maps to a DBMS column. A derived attribute is a combination of other attributes and does not directly map to a DBMS column. A relationship creates a link between entities of the model. A relationship can be used to flatten an attribute or flatten a relationship.Type: GrantFiled: March 5, 2003Date of Patent: October 24, 2006Assignee: Apple Computer, Inc.Inventors: Richard Williamson, Linus Upson, Jack Greenfield, Daniel Willhite
-
Publication number: 20060095524Abstract: The present invention provides systems, methods, computer program products, and combinations and subcombinations thereof for filtering received messages. The invention includes a client system having filtering logic, a statistical classifier module, and a classifier database. The classifier module is automatically trained, without manual intervention, when the score generated by the classifier for a received message is inconsistent with a user-defined authoritative status indication. In addition, the classifier module is initialized using user-identified messages in a ratio representative of the ratio of non-spam to spam messages received by the user.Type: ApplicationFiled: October 7, 2005Publication date: May 4, 2006Inventors: Erik Kay, David Moore, Daniel Willhite, Linus Upson
-
Publication number: 20060080303Abstract: A system, method and computer program product provide a search module for searching digital data. The search module operates, according to an embodiment, by indexing stored data without interrupting use of the stored data, synchronizing the indexed data with data stored subsequent to the indexing step, searching at least one of the synchronized data and the indexed data, and outputting results of the searching step.Type: ApplicationFiled: October 7, 2005Publication date: April 13, 2006Applicant: Computer Associates Think, Inc.Inventors: Antony Sargent, Erik Kay, David Moore, Daniel Willhite, Linus Upson
-
Publication number: 20060026562Abstract: A method for providing stand-in objects, where relationships among objects are automatically resolved in an object oriented relational database model without the necessity of retrieving data from the database until it is needed. A “fault” class is defined, as well as fault objects whose data haven't yet been fetched from the database. An object that's created for the destination of a relationship whenever an object that includes the relationship is fetched from the database. When an object is fetched that has relationships, fault objects are created to “stand-in” for the destination objects of those relationships. Fault objects transform themselves into the actual enterprise objects—and fetch their data—the first time they're accessed. Subsequently, messages sent to the target objects are responded to by the objects themselves.Type: ApplicationFiled: September 23, 2005Publication date: February 2, 2006Inventors: Richard Williamson, Linus Upson, Daniel Willhite, Jack Greenfield
-
Patent number: 6952706Abstract: A method for providing stand-in objects, where relationships among objects are automatically resolved in an object oriented relational database model without the necessity of retrieving data from the database until it is needed. A “fault” class is defined, as well as fault objects whose data haven't yet been fetched from the database. An object that's created for the destination of a relationship whenever an object that includes the relationship is fetched from the database. When an object is fetched that has relationships, fault objects are created to “stand-in” for the destination objects of those relationships. Fault objects transform themselves into the actual enterprise objects—and fetch their data—the first time they're accessed. Subsequently, messages sent to the target objects are responded to by the objects themselves. This delayed resolution of relationships occurs in two stages: the creation of a placeholder object for the data to be fetched, and the fetching of that data only when it's needed.Type: GrantFiled: September 5, 2002Date of Patent: October 4, 2005Assignee: Apple ComputerInventors: Richard Williamson, Linus Upson, Daniel Willhite, Jack Greenfield
-
Publication number: 20050114863Abstract: The present invention comprises a method for allowing a data controlling object to interface with any number of user interface objects without requiring separate interface code for each user interface object and without restricting the user interface to certain predetermined designs. The present method provides objects called association objects that are interposed between a data controlling object and each user interface object. Each kind of user interface object has a corresponding association object. The association object for a particular kind of user interface object contains code that allows the association object to interact with the specific kind of user interface object with which it is associated. Each association object also presents a standard interface to a data controlling object, regardless of the kind of user interface object with which the association object is associated.Type: ApplicationFiled: September 28, 2004Publication date: May 26, 2005Inventors: Richard Williamson, Linus Upson, Jack Greenfield, Daniel Willhite
-
Publication number: 20050034132Abstract: A method for providing stand-in objects, where relationships among objects are automatically resolved in an object oriented relational database model without the necessity of retrieving data from the database until it is needed. A “fault” class is defined, as well as fault objects whose data haven t yet been fetched from the database. An object that's created for the destination of a relationship whenever an object that includes the relationship is fetched from the database. When an object is fetched that has relationships, fault objects are created to “stand-in” for the destination objects of those relationships. Fault objects transform themselves into the actual enterprise objects—and fetch their data—the first time they're accessed. Subsequently, messages sent to the target objects are responded to by the objects themselves. This delayed resolution of relationships occurs in two stages: the creation of a placeholder object for the data to be fetched,. and the fetching of that data only when it's needed.Type: ApplicationFiled: September 5, 2002Publication date: February 10, 2005Inventors: Richard Williamson, Linus Upson, Daniel Willhite, Jack Greenfield
-
Patent number: 6820268Abstract: The present invention comprises a method for allowing a data controlling object to interface with any number of user interface objects without requiring separate interface code for each user interface object and without restricting the user interface to certain predetermined designs. The present method provides objects called association objects that are interposed between a data controlling object and each user interface object. Each kind of user interface object has a corresponding association object. The association object for a particular kind of user interface object contains code that allows the association object to interact with the specific kind of user interface object with which it is associated. Each association object also presents a standard interface to a data controlling object, regardless of the kind of user interface object with which the association object is associated.Type: GrantFiled: August 29, 2002Date of Patent: November 16, 2004Assignee: NeXT Computer, Inc.Inventors: Richard Williamson, Linus Upson, Jack Greenfield, Daniel Willhite
-
Patent number: 6704744Abstract: The present invention creates a model that maps object classes in an object-oriented environment to a data source. The model maps the relationship between properties of each object class and data of the data source. The present invention can be used with a data source such as a relational database, user interface, file system, or object-oriented database. An application's object classes and data source schema are designed independent of the other since the model can be used to map one to the other. The model is comprised of entities and attributes. An entity maps to an object class and to at least one table of the DBMS. An entity contains attributes either simple or derived. A simple attribute maps to a DBMS column. A derived attribute is a combination of other attributes and does not directly map to a DBMS column. A relationship creates a link between entities of the model. A relationship can be used to flatten an attribute or flatten a relationship.Type: GrantFiled: September 18, 2000Date of Patent: March 9, 2004Assignee: NeXT Computer, Inc.Inventors: Richard Williamson, Linus Upson, Jack Greenfield, Daniel Willhite
-
Patent number: 6513072Abstract: The present invention comprises a method for allowing a data controlling object to interface with any number of user interface objects without requiring separate interface code for each user interface object and without restricting the user interface to certain predetermined designs. The present method provides objects called association objects that are interposed between a data controlling object and each user interface object. Each kind of user interface object has a corresponding association object. The association object for a particular kind of user interface object contains code that allows the association object to interact with the specific kind of user interface object with which it is associated. Each association object also presents a standard interface to a data controlling object, regardless of the kind of user interface object with which the association object is associated.Type: GrantFiled: October 30, 2000Date of Patent: January 28, 2003Assignee: Next Computer, Inc.Inventors: Richard Williamson, Linus Upson, Jack Greenfield, Daniel Willhite
-
Publication number: 20020199029Abstract: The present invention comprises a method for allowing a data controlling object to interface with any number of user interface objects without requiring separate interface code for each user interface object and without restricting the user interface to certain predetermined designs. The present method provides objects called association objects that are interposed between a data controlling object and each user interface object. Each kind of user interface object has a corresponding association object. The association object for a particular kind of user interface object contains code that allows the association object to interact with the specific kind of user interface object with which it is associated. Each association object also presents a standard interface to a data controlling object, regardless of the kind of user interface object with which the association object is associated.Type: ApplicationFiled: August 29, 2002Publication date: December 26, 2002Inventors: Richard Williamson, Linus Upson, Jack Greenfield, Daniel Willhite