That's a pretty reasonable argument and I believe a big part of what makes hooks somewhat complex since they look like regular Javascript but can behave differently.
There are elements of the article that argue against that though. It argues that the index.html will be small (and thus not an issue to not cache), which will not be the case if you're server-rendering pages.
Allow for more than one attacker.
That's what they suggest at the end of the article.
All the time. I usually have a couple of fiction books going at any given time and finish 1-2 a week. I'll pick up the occasional magazine and often have a non-fiction or technical book going as well.
Are you looking at making the video's available using the HTML5 <video> tag? Because I don't have Flash installed locally (or on my iPhone) there's nothing much to see there right now.
That's a pretty reasonable argument and I believe a big part of what makes hooks somewhat complex since they look like regular Javascript but can behave differently.
There are elements of the article that argue against that though. It argues that the index.html will be small (and thus not an issue to not cache), which will not be the case if you're server-rendering pages.
Allow for more than one attacker.
That's what they suggest at the end of the article.
All the time. I usually have a couple of fiction books going at any given time and finish 1-2 a week. I'll pick up the occasional magazine and often have a non-fiction or technical book going as well.
Are you looking at making the video's available using the HTML5 <video> tag? Because I don't have Flash installed locally (or on my iPhone) there's nothing much to see there right now.