|Numéro de publication||US7051031 B2|
|Type de publication||Octroi|
|Numéro de demande||US 09/973,784|
|Date de publication||23 mai 2006|
|Date de dépôt||9 oct. 2001|
|Date de priorité||9 oct. 2001|
|État de paiement des frais||Payé|
|Autre référence de publication||US20040107405|
|Numéro de publication||09973784, 973784, US 7051031 B2, US 7051031B2, US-B2-7051031, US7051031 B2, US7051031B2|
|Inventeurs||Phillip Mark Schein|
|Cessionnaire d'origine||Sun Microsystems, Inc.|
|Exporter la citation||BiBTeX, EndNote, RefMan|
|Citations de brevets (21), Citations hors brevets (3), Référencé par (36), Classifications (17), Événements juridiques (4)|
|Liens externes: USPTO, Cession USPTO, Espacenet|
1. Field of the Invention
The present invention relates to a method, system, and program for managing accesses to data objects by multiple user programs over a network.
2. Description of the Related Art
In network environments where multiple users can access a single file, the file system includes a locking scheme to manage access to a file to maintain data integrity and avoid consistency problems by preventing two or more users from simultaneously modifying a file. Many application programs, such as database programs, also employ a locking scheme to maintain data integrity by preventing multiple users from modifying application data in a manner that will harm data consistency. For instance, database programs perform locking on a record-by-record basis to prevent multiple users from simultaneously modifying the same record.
In many systems, once a user has an exclusive lock on a file, that user can prevent others from modifying the file for a significant amount of time until the user releases the lock. One problem with such systems is that after obtaining a lock, the user may delay performing the intended modification and during such delay prevent other applications from modifying the data.
Moreover, locking schemes also require that the file system or application program manage various data structures to keep track of the users that maintain a lock and other users that should receive the lock upon its release, as well as timeout a lock if the holder of the lock has not performed any action within a predetermined time period. The burden of managing locks increases as the number of files or records that can be separately locked increases.
For all these reasons, there is a need in the art for improved data object locking schemes.
Provided is a method, system, and program for managing access to data objects by multiple user programs over a network. A page is generated including at least one editable field of data from at least one data object. An initial value is calculated from the at least one data object and the page and the initial value are transmitted to one user program over the network. The page and the initial value are received from the user program, wherein the received page includes modified data in at least one editable field. A current value is calculated from the at least one data object after receiving the page and a determination is made as to whether the initial value transmitted with the received page is different than the current value. If the initial and current values match, then the data object is updated with the modified data included in the received page.
Further, the data object is not updated with the modified data in the received page if the initial and current values do not match.
In further implementations, the page includes multiple editable fields and each of the editable fields correspond to one of a plurality of data objects. In such case, the value is calculated from the plurality of the data objects, whereby a modification to one of the plurality of data objects between a time the initial value and current value are calculated will cause the initial value to differ from the current value.
In still further implementations, the page includes multiple editable fields and each of the editable fields corresponds to one of a plurality of data objects. In such case, calculating the initial value further comprises calculating a plurality of initial values, wherein each initial value is calculated from at least one data object corresponding to at least one editable field in the page. Further, calculating the current value further comprises calculating a plurality of current values, wherein each current value is calculated from at least one data object corresponding to at least one editable field in the page. Still further, determining whether the initial value transmitted with the received page is different than the current value is performed for each of the plurality of initial and current values and updating the data object with the modified data included in the received page further comprises updating each data object used in the calculation of the matching initial and current values with the modified data included in the received page.
In still additional implementations, information is generated on groups of the data objects corresponding to editable fields in the page, wherein each group comprises at least one data object corresponding to one editable field in the page. In such case, one initial value is calculated for each group from the data objects in the group.
Referring now to the drawings in which like reference numbers represents corresponding parts throughout:
In the following description, reference is made to the accompanying drawings which form a part hereof, and which illustrate several embodiments of the present invention. It is understood that other embodiments may be utilized and structural and operational changes may be made without departing from the scope of the present invention.
In certain implementations, the view pages 12 a, b . . . n may comprise HTML or Extensible Markup Language (XML) pages including hypertext links to other view pages 12 a, b . . . n. Additionally, the view pages 12 a, b . . . n may be implemented in alternative multi-media formats, such as Joint Photographic Experts Group (JPEG), the Adobe Portable Document Format (PDF)**, PostScript**, tagged image file format (TIFF), etc. In such case the viewer 14 a, b . . . n would include the capability to render such alternative view page 12 a, b . . . n media format. In response to a request from one viewer 14 a, b . . . n for a particular view at a universe resource locator (URL) address, the information server 8 would access the data designated to be inserted into the requested view page 12 a, b . . . n from the data directories 10 in the manner described below and insert the accessed into the designated field in the view page 12 a, b . . . n. The information server 8 would then return the filled-in view page 12 a, b . . . n to the requesting client 2 a, b . . . n. **Abode and PostScript are trademarks of Abode Systems, Inc.
The clients 2 a, b . . . n include viewer programs 14 a, b . . . n, such as an HTML browser capable of downloading and rendering a page 12 a, b . . . n of content from the server 4 using a network transfer protocol, such as HTTP, etc. The clients 2 a, b . . . n may comprise any computing device known in the art, such as a personal computer, workstation, laptop computer, hand held computer, telephony device, mainframe, server, etc. The server 4 comprises a server-class machine or any other type of computing device capable of responding to data requests from the clients 2 a, b . . . n.
In certain implementations, the data directories 10 store user data across a plurality of files. For instance, a type of data maintained by the information manager 8 may be categorized as part of an information class, e.g., a project for which information is maintained in a project manager program; a type of e-mail box in an e-mail program; a category of accounting information (e.g., expense, income, equity, etc.). Each instance of the class would include related information, such as attribute values of the general class, where the attribute values may differ among the information class instances.
For instance, the general class directory 50 may comprise a calendar and each calendar instance may comprise a day, such that each subdirectory 52 is an instance of one day; the class may comprise an e-mail message for a particular e-mail box and the instance would comprise the type of e-mail box, e.g., send, drafts, inbox, delete, etc.
In one implementation, the information server 8 comprises a project manager. One general class would comprise a project class, and each instance provides information on a particular project. There would be a separate subdirectory for each project instance. Following are some examples of attribute files that provide the attribute values for each project class instance. The following names comprise the file extensions used for the attribute files.
Further provided is a details subdirectory 154 a, b . . . n (
Additional project instance subclass directories 100 b . . . n (shown in
The information server 8 would receive requests from the viewers 14 a, b . . . n for a view page 12 a, b . . . n providing access to project data in the data directories 10 or a page that includes fields in which the user may enter data for a project that will be stored in subdirectories and files of the data directories 10.
To return a view page 12 b . . . n including project data from the data directories 10, the information server 8 would access the data in the subdirectory files in a predefined manner to access particular information to insert into a user requested view 12 b . . . n to return to render in the client viewer 14 a, b . . . n.
The user at the client 2 a, b . . . n would select the submit changes button 278 displayed on the page 12 b in their viewer program 14 a, b . . . n to transmit the page 12 b including data entered in one or more of the entry fields 250–274. In response to receiving the page, the information server 8 would then create a new subdirectory 100 n+1 for the new project. For each entry field in which data is entered, the information server 8 would create the file corresponding to such data entry field and then implement the attribute value entered in the entry field 250–274 in the created files 104 n+1 . . . 144 n+1, where the added project comprises the (n+1)th project for which information is maintained in the projects directory 102. The information server 8 would further generate a calendar subdirectory for the new project subdirectory and add a day file for the day the project was created. Moreover, a details subdirectory for the new project subdirectoy would also be added. In this way, all the subdirectories and accompanying files are created for the project subdirectory being created. Additionally, there can be additional fields in the add project page 12 b for additional attributes and information which may be maintained in additional files in the project subdirectory.
Selection of the “Projects Interrupts/Delays” hypertext link 202 in the home page 12 a (
In certain implementations, all the above information would be maintained in the interrupts file 144 a, b . . . n for each interrupt to the project associated with the subdirectory 100 a, b . . . n including the interrupts file 144 a, b . . . n. The interrupt file 144 a, b . . . n would include, for each interrupt, each of the above attributes (type of delay, date, duration, and comments). In this way, the attribute file interrupts 144 a, b . . . n has an attribute that has multiple components and would include multiple instances of the components, one instance for each defined interrupt. The multiple components of the interrupt include the interrupt attributes, such as type of delay, date, duration, etc. Thus, certain of the attribute files may include only one value, e.g., the start month, or may include multiple instances, such as multiple interrupts. Further, each attribute value instance in the attribute file may itself be comprised of multiple components or sub-attribute values.
The information server 8 then accesses the interrupt summary page template and generates a page 12 d including, but not limited to, the generated table 332.
If (at block 358) the full view option is not selected, then a single row of data is displayed, instead of multiple rows, including such information as the project name from the .projname file 114 a, the manager name, start data, projected completion, percent completed, and status form other of the attribute files.
If (at block 364) the active projects link 204 (
If (from the no branch of block 364) the future projects link 208 (
In still further implementations, each task may be comprised of subtasks having a separate percentage complete for each subtask.
In further implementations, in response to the user selecting the statistic/metric link 210 (
As discussed, there may be additional subclasses of an information class. For instance, the calendar subclass of a project class provides a calendar view of a project. The calendar subdirectory 150 a . . . n (
The described implementations concerned a file architecture for storing information used by an application program. In the file architecture, the application data is stored in separate files, and then accessed to allow a user to enter information or view the application data dispersed throughout different files.
The described file architecture may be implemented using standard file data structures and file management commands supplied by the operating system. The information server 8 would make file management command calls to access the data dispersed through the files in the file architecture.
The described implementations can implement a robust information management program without requiring the use of a database application program because the database and data management is implemented in the file system directories. This aspect makes the described architecture highly portable to other systems because applications written for different operating systems may include the same logic, but just use the calls for the target operating system. Because the basic file management operations are very similar for different operating systems, creating different versions of the information manager program for different operating systems would only require modifying the file management calls, which are often very similar in operation.
Additionally, the described implementations communicate with the users using an open document format compatible with the viewer programs users are likely to already have installed on their client systems 2 a, b . . . n, e.g., web browsers. In such implementations, the users do not need to install any additional client programs on their machine because their viewer program is all that is needed. Implementing the system in this manner avoids the need to install special purpose database and interface software on both the clients and server because the described implementations exploit already existing installed viewer and network communication programs.
As discussed, a viewer program 14 a, b . . . n may render a page of data where the data in the page is derived from different files in the data directories 10. Further, the user may modify particular data and submit the page with the modified data to update the files corresponding to the modified data. In a multiuser environment, the information server 8 may provide a locking mechanism to prevent multiple viewers 14 a, b . . . n from simultaneously modifying the same files/data.
In certain implementations, the information server 8 encodes each view page 12 a, b . . . n (
The view page 12 i further includes a lock code 506 generated from the files 504 a, b . . . n that provide the data to the editable fields 502 a, b . . . n. In certain implementations, a checksum operation is performed, such as the Unix “/usr/ucb/sum” operation that generates a 16 bit checksum for a file. The information server 8 may calculate a single lock code value 506 based on the checksum of all the data files 504 a, b . . . n. In certain implementations, this lock code 506 is then embedded as a hidden code in the view page 12 j, and not displayed or rendered by the viewer 14 a, b . . . n. When the viewer 14 a, b . . . n transmits the view page 12 j back to the information server 8 with modified data in the editable fields 502 a, b . . . n, the information server 8 would then determine, in the manner described below, whether the data files 504 a, b . . . n have changed since the view page 12 j was generated by the information server 8 to prevent changes to files that have received an intervening modification.
As discussed, upon receiving the view page 12 j, the user of the viewer 14 a, b . . . n may then modify one or more of the editable fields 502 a, b . . . n in the view page 12 j. The view page 12 j may include editable as well as read-only data fields generated from the files 504 a, b . . . n in the data directories 10. After the user has modified one or more of the editable fields 502 a, b . . . n in the view page 12 j displayed by the viewer 14 a, b . . . n, the user may select the submit button 508 to transmit the view page 12 j including fields 502 a, b . . . n having modified data to the information server 8.
In the described logic of
When generating the view page 712 having multiple lock codes in a page, the information server 8 would look at the lock code map 720 to determine the files 704 a, b . . . n referenced in the view page 712 editable fields 702 a, b . . . n associated with lock codes 706 a, b . . . n. The checksum operation at block 604 in
From blocks 762 or 764 control proceeds (at block 766) back to block 752 to consider the next lock code 706 a, b . . . n in the received view page 712 until all lock codes in the view page 712 are considered. After considering all lock codes 706 a, b . . . n in the view page 712, a determination is made as to whether (at block 768) a message was generated including the name of editable fields 702 a, b . . . n corresponding to files 704 a, b . . . n associated with lock codes that were not validated, i.e., lock codes that did not match the recalculated checksum for the files 704 a, b . . . n associated with the lock code 706 a, b . . . n. If such a message was generated, then the information server 8 adds content to inform the user that any changes entered for the following named data fields 702 a, b . . . n were not made due to possible intervening modifications. The message may also inform the user to refresh the view page 712 to view any changes to the data in the editable fields 702 a, b . . . n and resubmit any changes that could not be made on the previous submission.
The described implementations provide a locking mechanism that does not require the central information server 8 to maintain locking information. Instead, the locking information needed to determine if changes were made is encoded in the page transmitted or otherwise provided to the multiple users. With the described implementations, user modifications are not applied to files if the modified file is associated with a group of files that received intervening modifications from other users. Further, with the described implementations no one user can lockout or prevent another user from submitting changes because changes are made on a first-come, first serve basis. Users that have pages outstanding at the time the first user submits changes with respect to a group of data fields associated with a group of files would be blocked from submitting changes to the same group of data fields and files, and required to refresh the page and receive the modified data before their changes will be accepted.
Still further, in certain implementations where the locking data is maintained in the remote pages, a failure or crash of the information server 8 will not comprise a loss of the locking data. When the information server 8 again becomes operational it can still perform the validation operations described with respect to
The described file management architecture may be implemented as a method, apparatus or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof. The term “article of manufacture” as used herein refers to code or logic implemented in hardware logic (e.g., an integrated circuit chip, Field Programmable Gate Array (FPGA), Application Specific Integrated Circuit (ASIC), etc.) or a computer readable medium (e.g., magnetic storage medium (e.g., hard disk drives, floppy disks, tape, etc.), optical storage (CD-ROMs, optical disks, etc.), volatile and non-volatile memory devices (e.g., EEPROMs, ROMs, PROMs, RAMs, DRAMs, SRAMs, firmware, programmable logic, etc.)). Code in the computer readable medium is accessed and executed by a processor. The code in which preferred embodiments are implemented may further be accessible through a transmission media or from a file server over a network. In such cases, the article of manufacture in which the code is implemented may comprise a transmission media, such as a network transmission line, wireless transmission media, signals propagating through space, radio waves, infrared signals, etc. Of course, those skilled in the art will recognize that many modifications may be made to this configuration without departing from the scope of the present invention, and that the article of manufacture may comprise any information bearing medium known in the art.
In the described implementations, the view pages 12 a, b . . . n were implemented as HTML pages for display in a web browser type viewer. Additionally, the view pages 12 a, b . . . n may be in alternative media formats, such as Extensible Markup Language (XML) pages, Standard Generalized Markup Language (SGML) file, ASCII, etc. The described implementations utilize a browser program, such as a web browser capable of rendering HTML and other markup language content. However, any presentation program capable of rendering content in any media format may be used to render the state changes supplied by the server.
In the described implementations, the client and server used the HTTP protocol to communicate. In alternative implementations, the client and server may use any communication or messaging protocol known in the art to communicate.
The described implementations include one class type whose files are stored in a subdirectory of the main directory and one subclass for each class type, implemented as a subdirectory of the information class subdirectory. Additional information class types may be added at the same level providing different types of information and additional attribute files may be provided to store the values associated with the additional information classes.
The preferred logic of
In further implementations, an intervening modification check may be made when a user enters data into one of the editable fields whether the entered data conforms to the data type of the modified editable field. If the user entered data type is inconsistent with the data type of the editable field, then an error message may be returned indicating the reason for the error. This check may be performed by the viewer program while the view page is displayed at the client or may be performed by the information server when processing the editable fields in the returned view page.
In the described implementations, the editable fields in the view page transmitted to the viewer programs referenced data in multiple files and the lock code was associated with one or more of the files providing data to the data fields in the view page. In alternative implementations all the data fields may reference data in a single file, and the lock code embedded in the view page would be used to determine whether intervening changes were made to the one file supplying the data to the fields in the view page.
In the described implementations the lock code was encoded into the page content, such as a hidden value in an HTML page. In additional implementations, the lock code may be provided in a different manner. For instance, the lock code may be appended to the Universal Resource Locator (URL) address of the page transmitted to the information server 8. Still further, the lock code may be provided in a separate data object transmitted with the page.
In the described implementations, modified data entered in the editable fields of a returned view page may be added to the content of the files corresponding to the data fields, or if the data is maintained in the file name, then the name of the corresponding file would be modified.
In the described implementations, the data in the editable fields was obtained from files in a file system. In alternative implementations, the data in the editable fields may reference data objects other than files, such as records in a database system or any other program objects known in the art that may be separately accessed and updated.
The foregoing description of the preferred embodiments of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. It is intended that the scope of the invention be limited not by this detailed description, but rather by the claims appended hereto. The above specification, examples and data provide a complete description of the manufacture and use of the composition of the invention. Since many embodiments of the invention can be made without departing from the spirit and scope of the invention, the invention resides in the claims hereinafter appended.
|Brevet cité||Date de dépôt||Date de publication||Déposant||Titre|
|US5008853||2 déc. 1987||16 avr. 1991||Xerox Corporation||Representation of collaborative multi-user activities relative to shared structured data objects in a networked workstation environment|
|US5220657||15 avr. 1991||15 juin 1993||Xerox Corporation||Updating local copy of shared data in a collaborative system|
|US5247615||20 déc. 1990||21 sept. 1993||Hitachi, Ltd.||Control method and system for establishing a connection among terminals forming a joint project information processing system|
|US5293619||30 mai 1991||8 mars 1994||Sandia Corporation||Method and apparatus for collaborative use of application program|
|US5379374||21 nov. 1991||3 janv. 1995||Hitachi, Ltd.||Collaborative information processing system and workstation|
|US5446842||26 févr. 1993||29 août 1995||Taligent, Inc.||Object-oriented collaboration system|
|US5515491||31 déc. 1992||7 mai 1996||International Business Machines Corporation||Method and system for managing communications within a collaborative data processing system|
|US5649089 *||30 nov. 1994||15 juil. 1997||Motorola, Inc.||Method and apparatus for maintaining a redundant database system|
|US5799320||12 nov. 1992||25 août 1998||John R. Klug||Remote multiple-user editing system and method|
|US5890177||24 avr. 1996||30 mars 1999||International Business Machines Corporation||Method and apparatus for consolidating edits made by multiple editors working on multiple document copies|
|US5966512||5 juin 1997||12 oct. 1999||International Business Machines Corporation||Groupware save operation|
|US6044387||10 sept. 1997||28 mars 2000||Microsoft Corporation||Single command editing of multiple files|
|US6067551||14 nov. 1997||23 mai 2000||Microsoft Corporation||Computer implemented method for simultaneous multi-user editing of a document|
|US6073161||16 déc. 1997||6 juin 2000||International Business Machines Corporation||Method and apparatus for determining editing conflicts in a multi-authoring system|
|US6088702||25 févr. 1998||11 juil. 2000||Plantz; Scott H.||Group publishing system|
|US6266675 *||7 oct. 1997||24 juil. 2001||Phycom Corporation||System and method for using a relational database to enable the dynamic configuration of an application program|
|US6366933 *||27 oct. 1995||2 avr. 2002||At&T Corp.||Method and apparatus for tracking and viewing changes on the web|
|US6553388 *||20 juil. 2000||22 avr. 2003||International Business Machines Corporation||Database deltas using Cyclic Redundancy Checks|
|US20010011274 *||4 août 1998||2 août 2001||John R. Klug||World wide web registration information processing system|
|US20020013825 *||21 sept. 2001||31 janv. 2002||Freivald Matthew P.||Unique-change detection of dynamic web pages using history tables of signatures|
|US20030033241 *||8 août 2001||13 févr. 2003||Adi Harari||Methods and systems for automated loan origination, processing and approval|
|1||Bemers-Lee, T., and D. Connolly. "Hypertext Markup Language- 2.0- Forms". [online], Sep. 22, 1995. [Retreived on Oct. 5, 2002]. Retrieved from the Internet at <URL: http://www.w3.org/MarkUp/html-spec/html-spec<SUB>-</SUB>8.htm;#SEC8>.|
|2||Panagiotis, Christias. "Unix Man Pages: Sum (1B)." [online], Copyright 1999 Man -cgi 2.00. [Retrieved Sep. 3, 2001]. Retrieved from the Internet at <URL: http://www/ntua.gr/cgi-bin/man-cgi?sum+1B>.|
|3||U.S. Appl. No. 09/973,889, filed on Oct. 9, 2001, entitled, "Method, System, and Program for Managing Information for an Application Program Using a File Management System", invented by P.M. Schein.|
|Brevet citant||Date de dépôt||Date de publication||Déposant||Titre|
|US7512748 *||17 août 2006||31 mars 2009||Osr Open Systems Resources, Inc.||Managing lock rankings|
|US7523391 *||25 mars 2003||21 avr. 2009||Microsoft Corporation||Indicating change to data form|
|US7809897||19 févr. 2009||5 oct. 2010||Osr Open Systems Resources, Inc.||Managing lock rankings|
|US7895176 *||29 nov. 2006||22 févr. 2011||Red Hat, Inc.||Entry group tags|
|US7925246||24 oct. 2005||12 avr. 2011||Leader Technologies, Inc.||Radio/telephony interoperability system|
|US7945595||12 mai 2008||17 mai 2011||Adobe Systems Incorporated||System and method for generating an item list in electronic content|
|US7949633||24 mai 2011||Adobe Systems Incorporated||Shared edit access of electronic content|
|US7949693||24 mai 2011||Osr Open Systems Resources, Inc.||Log-structured host data storage|
|US8024433||20 sept. 2011||Osr Open Systems Resources, Inc.||Managing application resources|
|US8069228 *||17 août 2009||29 nov. 2011||Hewlett-Packard Development Company, L.P.||Preventing access of a network facility in response to an operation|
|US8195714||10 déc. 2003||5 juin 2012||Leaper Technologies, Inc.||Context instantiated application protocol|
|US8290902||6 avr. 2011||16 oct. 2012||Adobe Systems Incorporated||Shared edit access of electronic content|
|US8396900||6 avr. 2011||12 mars 2013||Adobe Systems Incorporated||System and method for editing an item list in electronic content|
|US8521752||3 juin 2005||27 août 2013||Osr Open Systems Resources, Inc.||Systems and methods for arbitrary data transformations|
|US8539228||24 août 2006||17 sept. 2013||Osr Open Systems Resources, Inc.||Managing access to a resource|
|US8635584 *||13 oct. 2009||21 janv. 2014||Yahoo! Inc.||Tutorial systems for code creation and provenance tracking|
|US8706760 *||28 févr. 2003||22 avr. 2014||Microsoft Corporation||Method to delay locking of server files on edit|
|US8768885||12 sept. 2012||1 juil. 2014||Adobe Systems Incorporated||Shared edit access of electronic content|
|US8849869||11 mars 2013||30 sept. 2014||Adobe Systems Incorporated||System and method for editing an item list in electronic content|
|US8893017||29 mai 2008||18 nov. 2014||Adobe Systems Incorporated||Tracking changes in a database tool|
|US8903874||2 nov. 2012||2 déc. 2014||Osr Open Systems Resources, Inc.||File system directory attribute correction|
|US8990228||22 juil. 2013||24 mars 2015||Osr Open Systems Resources, Inc.||Systems and methods for arbitrary data transformations|
|US8996621||12 mai 2008||31 mars 2015||Adobe Systems Incorporated||Asynchronous comment updates|
|US9176943||12 mai 2008||3 nov. 2015||Adobe Systems Incorporated||Comment presentation in electronic documents|
|US9280553||18 avr. 2014||8 mars 2016||Microsoft Technology Licensing, Llc||Method to delay locking of server files on edit|
|US9329744||12 mai 2008||3 mai 2016||Adobe Systems Incorporated||Segmented scroll bar|
|US9418054||12 mai 2008||16 août 2016||Adobe Systems Incorporated||Document comment management|
|US20030225831 *||30 mai 2003||4 déc. 2003||Arito Asai||Center server and computer apparatus|
|US20040172395 *||28 févr. 2003||2 sept. 2004||Microsoft Corporation||Method to delay locking of server files on edit|
|US20060277153 *||3 juin 2005||7 déc. 2006||Osr Open Systems Resources, Inc.||Systems and methods for arbitrary data transformations|
|US20060282504 *||19 janv. 2006||14 déc. 2006||Fuji Xerox Co., Ltd.||Usage status notification system|
|US20080126355 *||29 nov. 2006||29 mai 2008||Peter Andrew Rowley||Entry group tags|
|US20080270587 *||24 avr. 2007||30 oct. 2008||Mason W Anthony||Managing application resources|
|US20100287290 *||17 août 2009||11 nov. 2010||Richard Bramley||Virtual Hotplug Techniques|
|US20110088009 *||13 oct. 2009||14 avr. 2011||Yahoo! Inc.||Tutorial systems for code creation and provenance tracking|
|US20130019189 *||14 juil. 2011||17 janv. 2013||Cbs Interactive Inc||Augmented editing of an online document|
|Classification aux États-Unis||707/697, 715/234, 707/758, 707/959, 707/822, 707/999.01, 707/737, 707/999.2|
|Classification internationale||G06F15/16, G06F17/30, G06F9/46, G06F9/44|
|Classification coopérative||Y10S707/959, G06F9/52, G06F9/4443|
|Classification européenne||G06F9/52, G06F9/44W|
|9 oct. 2001||AS||Assignment|
Owner name: SUN MICROSYSTEMS, INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SCHEIN, PHILLIP MARK;REEL/FRAME:012253/0678
Effective date: 20011001
|21 oct. 2009||FPAY||Fee payment|
Year of fee payment: 4
|23 oct. 2013||FPAY||Fee payment|
Year of fee payment: 8
|14 déc. 2015||AS||Assignment|
Owner name: ORACLE AMERICA, INC., CALIFORNIA
Free format text: MERGER AND CHANGE OF NAME;ASSIGNORS:ORACLE USA, INC.;SUN MICROSYSTEMS, INC.;ORACLE AMERICA, INC.;REEL/FRAME:037280/0221
Effective date: 20100212