<p>So I'm reading The Art &amp; Science of Javascript, which is a good book, and it has a good section on JSONP. I've been reading all I can about it today, and even looking through every question here on StackOverflow. JSONP is a great idea, but it only seems to resolve the "Same Origin Problem" for <i>getting</i> data, but doesn't address it for <i>changing</i> data. </p>

<p>Did I just miss all the blogs that talked about this, or is JSONP <strong>not</strong> the solution I was hoping for?</p>

JSONP results in a SCRIPT tag being generated to another server with any parameters that might be required as a GET request. e.g.
```
```
<script src="http://myserver.com/getjson?customer=232&callback=jsonp543354" type="text/javascript">
</script>
```
```
There is technically nothing to stop this sort of request altering data on the server, e.g. specifying newName=Tony.  Your response could then be whether the update succeeded or not.  You will be limited by whatever you can fit on a querystring.  If you are going with this approach add some random element as a parameter so that proxy's won't cache it.
Some people may consider this goes against the way GET's are supposed to work i.e. they shouldn't cause data to change.