How can it be enforced? Any suggestions?
Users can also make it a bit more complicated while using `*` to get hacked by accepting responses which match some kinda pattern(it's not bullet-proof though) and simply discarding others.
All boils down the sender using a specific target, and the receiver remembering to check the origin.
To view a heatmap, user has to enter a URL, select date-range(Optional), and select the segmentation(eg. Direct, Referral, Location, Device, etc.)(optional).
A new tab is opened up with the specified URL each time on clicking the generate button.
So, let's say, you have to view heatmap of your site for:
1.The last week and only for those who live in US
2. The last week and only for those who uses Windows
3. The last month and who came directly to your site
4. The entire duration of the campaign and for all users
Now, for each configuration, there's an opened tab with the specified URL opened in it and the data for the requested segments and dates.
To pass on the data to and fro from one tab to another, and to track the status of all tabs(active/close), to notify other tabs when one gets closed, to notify all the children tabs when the opener tab gets closed, to send a message to a specific tab(eg. change segment) and to send a message to all tabs(eg. fetch data for new date applied), this library comes in handy. All this can be achieved with its simple API.
Hope you get the gist now.
Looking at Wingify's website it seems they're doing something similar with A/B testing - they (presumably) have an app that sits in one tab and a two of copies of the target site in two more tabs, so changes made in their app are reflected in the two versions of the target site. That's a total guess though.
Why we want this library, at Wingify, is something related to heatmaps and showing previews of changes made to the site in new tabs. Please read the detailed explanation I gave to @martin-adams in the above comment.