And here I was hoping that this was talk of APIs in general programming, not web-specific. Then again, I rarely see anything that's general programming on this site. Maybe I'll start submitting stories for interesting papers I read...
Yeah, as a "dinosaur" embedded systems programmer who works mostly in assembly/c, I am beginning to feel a big uncomfortable as to how the default mode of thinking when the word "programming" comes up is web programming. Perhaps I'm just too old(well, I'm 19, and an EE student...but it feels that way!)
Funnily enough I do know what an API is, and if Digg had a web dev category I would have put it there. Sorry it wasn't quite what you were looking for.
7methodsJul 3, 2006
Contains clear and concise information on getting around browser security restrictions that prevent cross site scripting.
daekenJul 3, 2006
And here I was hoping that this was talk of APIs in general programming, not web-specific. Then again, I rarely see anything that's general programming on this site. Maybe I'll start submitting stories for interesting papers I read...
Closed AccountJul 4, 2006
Yeah I was expecting something different!
kibibytebrainJul 4, 2006
Yeah, as a "dinosaur" embedded systems programmer who works mostly in assembly/c, I am beginning to feel a big uncomfortable as to how the default mode of thinking when the word "programming" comes up is web programming. Perhaps I'm just too old(well, I'm 19, and an EE student...but it feels that way!)
hjtalviJul 4, 2006
Because the author described it as an "how-to" article, the part on how to implement proxying was clearly justified.
lovefridaysJul 5, 2006Submitter
Funnily enough I do know what an API is, and if Digg had a web dev category I would have put it there. Sorry it wasn't quite what you were looking for.
mikeschinkelJan 14, 2007
Heh. If you'd actually read the article, you'd have seen that he presents a method by which you *don't* need a proxy.