i have a worst hosting provider.
due to some restrictions i can`t use ID
For Example i want to change change of heading.also,note this is not correct code but POSSIBLE code which is not working.
<!DOCTYPE html>
<html>
<body>
I am working on a offline Html5 web application. In this i use the HTML5 APPCACHE for offline purpose. I want to handle this cache functionality on user will. Means whenever a user visit this web application he will get the promt msg to change version if he choose to no then this application should work on old version of appcache (* After refreshing or reloading this web page should work on old version) Now if user choose yes the his application must use the new version………
I have search a lot for this put i can only listen the events of this appcache see this….
Abstract: Simple http2.0 fix would remove the GET size limitation.
Problem example: Say you have a search form, and instead of having to pass 100 characters to the report server, you need to pass 1,000 to GET a report.
Problem: If state information passed from page to page is small, (e.g. a simple web page request) then GET works fine. But when state information is larger than will fit in a URI, (i.e. more complex web requests), then either a session variable or POST must be used to pass the state information. Session variables time out and POST is idempotent and thus not suited to only passing state. Either way the most basic idea of web statefulness for complex non-idempotent page requests is currently broken.
This is what commonly causes the widely discussed IE “Webpage has expired” error when the browser back button is used on a complex page request. It should be noted that IE is faithfully following the standards, but that the standard itself is limiting.
Other browsers (FireFox, Chrome, Opera, and Safari) return the previously cashed page rather than report the possible problem which makes complex pages work, but is not really the best thing either because it puts the user at risk of double purchases. Furthermore, for pages to be browser independent they must be dumbed down to suit the IE method.
Proposed solution: Add a new non-idempotent method (similar to GET), for the moment let’s call it “STATE” to signify that you are simply passing some state data, and not making a data base update. Have it functionally work like “POST” in how it passes the variables in the header, i.e. with no size constraint, but be designated like GET in being treated as non-idempotent by browsers, so as to not cause expired warnings.
Issues: This will not allow bookmarking the page request as you can do with a GET request. For applications that need that capability GET will still exist. It is not reasonable to simply up the size of a URI string as it has too many other implications.
_______
Hope this makes sense to a few of you. It’s my first suggestion to W3C after 17 years of web development.
I want to find a method to expose the behavior of an agent for the “Madkit” platform as a web service. Does someone has a proposal of a theoretical solution that allows us to do that?
je veux trouver une méthode qui permet d’exposer les comportements d’un agent, pour le plateforme “Madkit”, sous forme service web. Est ce que quelqu’un a une proposition d’une solution théorique qui nous permet de faire ça?
We all know that the computational performance of the code generated by modern ECMAScript JIT/AOT engines is very high, and for most purposes “good enough”. In fact, I have encountered several situations where my JavaScript code runs as fast as (or even faster than) the corresponding optimized compiled C++ code (g++ -O3).
Still, there are situations when this is not enough. For instance, in real time audio processing you want to minimize latencies and CPU load as far as possible.
One way to increase the performance and reduce latencies is to utilize the instruction level parallelism that is available in modern CPU architectures through SIMD instructions. On the other hand, it is very difficult to make use of these instructions in a platform agnostic language such as ECMAScript (see [1] and [2], for instance).
The River Trail proposal from Intel solves the parallelism issue by introducing the new data type ParallelArray, upon which fairly generic ECMAScript operations can operate. While this is a nice and quite generic solution, it adds some fairly heavy requirements on the ECMAScript compiler.
I decided to make an attempt at creating a partial solution that is easy to integrate into current Web clients, yet powerful enough to solve many problems (especially related to signal processing).
Situations of interrupted work caused by accidental loss of connectivity or by intentional offline work are very frequent. Concerned by the negative effects of interruptions in users’ activities, we are investigating a new approach for the design and development of Web applications resilient to interruptions. In order to help users to recover from interruptions whilst navigating Web sites we propose a model-based approach that combines explicit representation of end-user navigation, local information storage (i.e. Web browser caching mechanism) and polices for client-side adaptation of Web sites.
One of the key elements of our approach is the automatic generation of HTML. This HTML code includes specific attributes for adapting Web pages to cope with offline navigation.
Our aim is to discuss the use of such us attributes and / or the inclusion of new HTML elements within the standard for supporting offline interaction with web sites resilient to interruptions.
I’m following in recent months the Schema.org (http://schema.org/) developed by Bing, Google and Yahoo! Schema.org is a metadata vocabulary to mark up content web pages.
In my opinion, the project has many possibilities to success because has the support of the three most important web engines. But it also has some controversial aspects I would like to share with you.
On is Schema.org is developed outside the framework of W3C, when W3C is leading the Semantic Web from many years, and also Microsoft, Google and Yahoo! are members of the consortium. This apparently contradiction is reflected in the choice of Microdata (http://www.w3.org/TR/microdata/) as mark-up syntax instead of RDFa (http://www.w3.org/TR/rdfa-primer/), the syntax promoted by W3C.
Maybe the reason is that Schema.org and Linked Data (W3C) have different goals to mark-up web content, but on the other hand Schema.org is collaborating with W3C and RDFa Lite as we can see in http://blog.schema.org/2011/11/using-rdfa-11-lite-with-schemaorg.html. Then, maybe their goals aren’t so different?
I’d like to shed the light on Hyper Application Markup Language. It will describe a structure of the entire web application. Relations and transitions between HTML documents without HTML markup. I have a draft example of what I mean:
As you can see the markup will describe relations between pages inside a web application instead of describing a single HTML document.
I have a prototype application that uses the same principles and similar markup on the execution background.
The application is represent by a lot of small components aka pages that communicate between each other using a similar approach (by firing events). It allows extending the application by introducing new page components and using the markup to wire them into the application. The application is extra flexible and by using the markup I can expose a subset of pages so they will look like a smaller application.
I’m going to create a community group around this topic and to create a comprehensive standard that will unify and simplify web application development around the world.
<script type="text/javascript" src="http://thc-racing.ucoz.com/design/forum-external/xdm/easyXDM.js"></script> <div id="page-body"> <!-- do not define an iframe, it will get generated for you in this container --> </div> <script type="text/javascript"> new easyXDM.Socket({ remote: "http://thc-racing.forumotion.co.uk/", container: document.getElementById("page-body"), onMessage: function(message, origin){ this.container.getElementsByTagName("iframe")[0].style.height = message + "px"; this.container.getElementsByTagName("iframe")[0].style.width = "900px"; } }); </script>
iFramed page:
<script type="text/javascript" src="http://thc-racing.ucoz.com/design/forum-external/xdm/easyXDM.js"></script> <script type="text/javascript"> var socket = new easyXDM.Socket({ onReady: function() { // this is needed for setting height on initial load socket.postMessage(document.body.scrollHeight) }, onMessage: function(message, origin){ // this is called from consumer (maybe by a timer) socket.postMessage(document.body.scrollHeight) } }); </script>
Thanks.
This forum is historical. From 2011 to 2015 this Community Forum was used for discussion about potential groups. It was closed because most discussion in practice takes place on the main Community Group blog. Learn more.