THIRD PARTY APPLICATION COMMUNICATION API
A device for a website building system (WBS) includes a communication hub embedded in a page of a website built by the WBS to implement 2-way cross domain communication with direct addressing between at least two third party applications from different vendors, the at least two third party applications each having an instance within the page. The communication hub includes a smart identifier and addresser to identify and provide the direct addressing of source or target third party applications between the at least two third party applications and to maintain a table of all absolute addresses for the 2-way cross domain communication; and a communication policy enforcer to enforce a communication policy between the WBS and the at least two third party applications to filter non-conforming communication according to the communication policy; and a protocol translator to provide 2-way interface translation between the at least two third party applications.
1 . A method for a website building system (WBS), the method comprising:
providing 2-way communication between at least a first third party application and a second third party application having instances in a page of a website of said WBS and, said page having components;
handling display changes in said page resulting from at least one dynamic layout event between said at least first third party application and said second third party application, wherein said handling display changes comprises changing the size and position of said components on said page in order to preserve the design of said page when said at least one dynamic layout event affects at least one component of said page; and
adapting said components according to said at least one dynamic layout event.
2 . The method according to claim 1 wherein said at least one dynamic layout event is at least one of: a changed view between different display devices; a rotation of a display device between portrait and landscape mode; a change the size or position of at least one component of said page and a content update of at least one component of said page.
3 . The method according to claim 2 wherein said content update is from at least one of: a server based update and a runtime update.
4 . The method according to claim 1 wherein said first third party application and said second third party application are at least one of a multi-party third party application and a modular third party application.
5 . The method according to claim 1 wherein said adapting comprises cascading style sheets.
6 . The method according to claim 1 wherein said 2-way communication is via at least one of an HTML5 (Hypertext Markup Language 5) PostMessage, a URL fragment identifier for messages, a specialized communication web service, an HTML5 local storage, an HTML5 local file system access APIs and a specialized browser plug in.
7 . The method according to claim 1 wherein said first third party application and said second third party application are embedded in said page using an iframe.
8 . The method according to claim 1 wherein said adapting comprises updating at least one of an attribute of said WBS, a control permission of at least one of: said at least first third party application and said second third party application and the layout, style and content of components of said page.
9 . A device for a website building system (WBS), the device comprising:
a communication hub embedded in a page of a website of said WBS to implement 2-way communication between at least a first third party application and a second third party application having instances in a page of said website, said page having components;
a dynamic layout handler to handle display changes in said page resulting from at least one dynamic layout event between at least said first third party application and said second third party application, wherein said dynamic layout handler changes the size and position of said components on said page in order to preserve the design of said page when said at least one dynamic layout event affects at least one component of said page; and
an updater to adapt said components according to said at least one dynamic layout event.
10 . The device according to claim 9 wherein said at least one dynamic layout event is at least one of: a changed view between different display devices; a rotation of a display device between portrait and landscape mode; a change the size or position of at least one component of said page and a content update of at least one component of said page.
11 . The device according to claim 10 wherein said content update is from at least one of: a server based update and a runtime update.
12 . The device according to claim 9 wherein said at least said first third party application and said second third party application are at least one of: a multi-party third party application and a modular third party application.
13 . The device according to claim 9 wherein said updater comprises cascading style sheets.
14 . The device according to claim 9 wherein said 2-way communication is via at least one of an HTML5 (Hypertext Markup Language 5) PostMessage, a URL fragment identifier for messages, a specialized communication web service, an HTML5 local storage, an HTML5 local file system access APIs and a specialized browser plug in.
15 . The device according to claim 9 wherein said at least first third party application and said second third party application are embedded in said page using an iframe.
16 . The device according to claim 9 wherein said updater adapts at least one of an attribute of said WBS, a control permission of at least one of: said at least first third party application and said second third party application and the layout, style and content of components of said page.