System for synchronization of changes in edited websites and interactive applications
A system for modifying a website or interactive application, including a published database accessible via an end user data service to present the most up to date version of objects of the website, viewable and editable by at least one user, a draft database accessible via a designer data service and viewable and editable by at least one designer to store edits to the objects of the published database; a published database request handler to coordinate concurrent viewing and updating of the objects between the end user data service and the published database and a draft database request handler to coordinate concurrent viewing, editing and updating of the objects between the designer data service and the draft database and to merge edits and updates to the objects in both the published database and the draft database and to return the merged version of the objects without modifying the published database.
1. A system for modifying a website or interactive application, said system comprising:
a processor; and
a unit running on said processor for managing amendments to a currently edited website from at least two sources when said website is running, said website comprising components including at least one list item stored in a list item repository, said unit comprising:
a published database to present a current published state of components of said website;
a draft database accessible, viewable and editable by said at least two sources to store at least edits to said components of said published database; and
an auxiliary system, to update said published database according to said edits, wherein said auxiliary system comprises:
an auto updater to notify at least a first source as to changes made to said currently edited website by a second source and to merge said changes to said currently edited website;
a publisher to publish designer changes held in said draft database to said published database; and
a reverter to execute revert requests,
wherein said publisher and said reverter exclude at least one list item according to a criteria comprising at least explicit specification by a designer of said application and size of said list item repository.
2. The system according to claim 1 and further comprising an archiver to access an archive database to read and write archived versions of said website, wherein said archiver also excludes said at least one list item according to said criteria.
3. The system according to claim 1 wherein a single list item comprises at least one of: items constructed according to single schema version, items constructed according to multiple versions of a given schema and items constructed according to multiple schemas.
4. The system according to claim 3 and further comprising an item adapter to adapt a list item to a different schema version.
5. The system according to claim 1 , wherein said criteria further comprise a pattern of use of said at least one list item.
6. The system according to claim 1 , wherein said criteria further comprise a frequency and scope of updates to said at least one list item.
7. The system according to claim 1 , wherein said criteria further comprise a classification of users accessing said at least one list item for modification.
8. The system according to claim 1 , wherein said auto updater further comprises a conflict resolver to resolve conflicts caused by incoming edits to said website from said at least two sources.
9. The system according to claim 8 , wherein said conflict resolver comprises a component comparer and merger to perform component oriented comparison and merging to determine different versions of components, resolve any differences and merge versions into a new updated version.
10. The system according to claim 1 , wherein said auxiliary system further comprises an editing history recorder to record editing history during editing into an editing history database.
11. A method for modifying a website or interactive application, said method comprising:
managing amendments to a currently edited website from at least two sources when said website is running, said website comprising components including at least one list item stored in a list item repository;
presenting a current published state of components of said website in a published database;
storing at least edits to said components of said published database in a draft database accessible, viewable and editable by said at least two sources;
updating said published database according to said edits using an auxiliary system, wherein said updating comprises:
notifying at least a first source as to changes made to said currently edited website by a second source and merging said changes to said currently edited website;
publishing designer changes held in said draft database to said published database; and
executing revert requests,
wherein said publishing and said executing revert requests exclude at least one list item according to a criteria comprising at least explicit specification by a designer of said application and size of said list item repository.
12. The method according to claim 11 , further comprising accessing an archive database to read and write archived versions of said website, wherein said accessing also excludes said at least one list item according to said criteria.
13. The method according to claim 11 , wherein a single list item comprises at least one of: items constructed according to single schema version, items constructed according to multiple versions of a given schema and items constructed according to multiple schemas.
14. The method according to claim 13 , further comprising adapting a list item to a different schema version.
15. The method according to claim 11 , wherein said criteria further comprise a pattern of use of said at least one list item.
16. The method according to claim 11 , wherein said criteria further comprise a frequency and scope of updates to said at least one list item.
17. The method according to claim 11 , wherein said criteria further comprise a classification of users accessing said at least one list item for modification.
18. The method according to claim 11 , wherein said notifying and merging further comprises resolving conflicts caused by incoming edits to said website from said at least two sources.
19. The method according to claim 18 , wherein said resolving conflicts comprises performing component oriented comparison and merging to determine different versions of components, resolve any differences and merge versions into a new updated version.
20. The method according to claim 11 , further comprising recording editing history during editing into an editing history database.