Even in the most simple tutorial you can find the use of protocols. It will certainly happen to many in your view controller to use a protocol, inputting, next to the definition of the interface, a statement similar to:
1 2 3 | UIViewController <uiwebviewdelegate> { @ Interface myViewController: UIViewController {<uiwebviewdelegate> ... } |
One consideration, obvious but overlooked during the development of applications in Adobe Flash, the difference between the player used for testing within the IDE Flash and the object (ActiveX or EMBED) used by your browser. Who owns the version "Macromedia" Flash MX (version 8 to be precise, but this discussion really applies to any version of Flash ...) when developing a movie and try it within the IDE runs the Flash Player linked to development package. Then when you publish your movie on the net and you "test" with the Flash Player browser you may experience some - substantial - differences!
 |  |
The development of web applications with Ajax-type technologies has highlighted the limitations of all Internet protocol HTTP. Sooner or any programmer trardi collides with the need - for example - to have a permanent connection with the client. Sending a broadcast to the client message is still impossible without resort to some artifice risky!
In the Internet scenario, however, the use of special components such as ActiveX Object, Flash or Java applet, allowing to circumvent the problem well. Often, in fact, one wonders if the HTTPRequest object (brick base for Ajax experience) can not be substituted by an ActiveX component or by using an invisible Flash movie just in case!
This is one of the most poignant part of the development of next-generation web applications. To prove it, in fact, there are a number of "beta" web application using mixed technologies to solve the various problems that arise - and that the HTTPRequest is unable to perform. The same FlickR , one of the most successful photo-blog, makes use of Flash movies in some sections of the site. There are actually more articulate where there are Java applets or ActiveX controls to get them where no one - Ajax - was gone before!
What should be done in the short term, is a new standard for the HTTPRequest, even calling it another way. Being able to get an object, present in all browsers, capable of making connections permanet and able to handle multiple protocols. However, this would be a pipe dream for developers, but reason well, could lead to death of the Internet as we know it.
When HTTP was designed as a global network we know today had very different speeds and users. The important points of HTTP are:
The HTTP is born with the basic idea of not burdening the network transmission; minimal support handshake! Even today, when the browser requests a page to a Web Server, the place just three steps above. It 'important to note that Google has developed a software like Google Earth in order to overcome the obstacles of connection and other stuff. Internet connection is ready to bear permanet? We think it's premature. Most hosting will collapse in a few seconds. Banda and CPU should be much more able to withstand the amount of traffic that is produced today.
The fact that support connections permanet are well circumscribed, and always make use of specific technologies and components, and sophisticated.
Latest Comments
Simon : It annoys disturbed again and use that space for these things ... however it does not work ...
Giovambattista Fazioli : @ Simon: what could be due to the syntax I used, specifically for PHP 5 +,...
Simon : I tried last night putting everything into functions.php, okay, jquery forms, and tabs jQueryUI them ...
Giovambattista Fazioli : @ Simon: I recommend cleaning to enter a code like that in ...
Simon : @ Giovambattista Fazioli: Thank you for your patience, it's all clear ... now I feel now, ...