Anant Garg | on web development

[...] . But why does the WSJ article only talk about Safari? Safari, by default, does not allow third-party cookies to be created. However, most major browsers- Firefox, Internet Explorer (using the correct [...]

[...] . But why does the WSJ article only talk about Safari? Safari, by default, does not allow third-party cookies to be created. However, most major browsers- Firefox, Internet Explorer (using the correct [...]

[...] cookies set on siteA.com cannot be read by siteB.com. So the work-around used is to store a third-party cookie (i.e. a cross-domain cookie). When a user visits siteA.com, a cookie is not only set for [...]

[...] cookies set on siteA.com cannot be read by siteB.com. So the work-around used is to store a third-party cookie (i.e. a cross-domain cookie). When a user visits siteA.com, a cookie is not only set for [...]

[...] Enable multiple users to post to a single collaborative twitter account. Why would you need such a program? 1. You [...]

[...] might work slightly erratically because the username is actually not supposed to be used by multiple users at the same time) Sample Chat User One Sample Chat User Two Sample Chat User Three Getting [...]

[...] Enable multiple users to post to a single collaborative twitter account. [...]

[...] Enable multiple users to post to a single collaborative twitter account. Why would you need such a program? 1. You [...]

[...] -up article regarding Google’s iPhone Tracking The Problem Safari does not allow cross-domain cookies. In other words, if on X.com, you load an iFrame with contents of Y.com and set a cookie [...]

[...] Safari does not allow cross-domain cookies. In other words, if on X.com, you load an iFrame with contents of Y.com and set a cookie [...]

[...] -up article regarding Google’s iPhone Tracking The Problem Safari does not allow cross-domain cookies. In other words, if on X.com, you load an iFrame with contents of Y.com and set a cookie [...]

[...] audience. I was referenced in the WSJ article- Google’s iPhone tracking regarding my cross-domain cookies post. For my technical audience, here is a detailed version of how my code was actually [...]

[...] that is done, you can safely commit your script (to the trunk folder). Be sure to commit the db folder, along with 1.sql. Note: When committing to your repository, make sure you do not commit any [...]

[...] to see output. Also before executing, import the database that I have created in the db folder. Suggestions? Do let me know your suggestions on how we can improve this code/any particular [...]

[...] your SQL DB, you simply update $currentdbversion & add the $currentdbversion.sql file to the db folder 4. When the app is run the next time, it will check if the SQL dbversion is lower than $ [...]

[...] : Option 1 – Single database, single code-base Use a single database and store all client data in a single database. You will have to add a field like “clientid” in all your [...]

[...] ” in the SQL query, it may result in issues with another client. Option 2 – Multiple database, single code-base Create a separate database for every client. No modification is required [...]