Linked by Thom Holwerda on Tue 23rd Mar 2010 16:26 UTC
Permalink for comment 414989
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
More News »
Sponsored Links



Member since:
2008-07-15
Not quite. The rendering etc is done server-side, but there's still a minimal local interpreter because it needs to be able to intercept javascript events and act on them. Even if all it does is forward the event to their server and send back the changed content, that's still enough grounds for Apple to reject as it's possible to run random 3rd party code in a 3rd party app.
Personally, I think Apple's controlling attitude is ridiculous, but the terms are very clear on this point at least. Many of their restrictions are arbitrary, but they seem pretty consistent with the no interpreters rule.