If you prefer a script on http://one-domain.com/ to have the ability to read in the database of http://another-domain.org then no -- the Same Origin Policy is used to localStorage and Web SQL databases, meaning only scripts running on a single domain because the script that produced the database are permitted to have the database.
Your best choice for the reason that situation is always to send the information from
one-domain to the server and also have the server of
one-domain push the information to
another-domain (otherwise, if they're on a single network, give a shared resource they are able to communicate over.)
You are able to make this happen by together with a utility iFrame having a database access script from b.com inside your a.com pages and the other way around. After that you can use mix document texting to transfer information. Observe that postMessage only sends an easy string and when you are attempting to pass structured information a.org and b.com will need to agree with a serialization. So...it is a hack.