Projects tagged ‘ajax’ and ‘xmlhttprequest’

DWR (Direct Web Remoting) is Easy Ajax for Java DWR enables Java code on the server and JavaScript code in a browser to interact and call each other as simply as possible, making it easy for ... [More] developers to add data into web pages. DWR generates JavaScript to allow web browsers to securely call into Java code almost as if it was running locally. It can marshall virtually any data including collections, POJOs, XML and binary data like images and PDF files. All that is required is a security policy defining allowed actions. With Reverse Ajax, DWR allows two-way interaction: browser calling server and server calling browser. DWR supports Comet, Polling and Piggyback as ways to publish to browsers. [Less]

qooxdoo is a comprehensive and innovative Ajax application framework. Leveraging object-oriented JavaScript allows developers to build impressive cross-browser applications. No HTML, CSS nor DOM ... [More] knowledge is needed. It includes a platform-independent development tool chain, a state-of-the-art GUI toolkit and an advanced client-server communication layer. It is Open Source under an LGPL/EPL dual license. [Less]

This javascript function creates an auto-complete field powered by PHP or whatever language you may want to use as your backend provider. It implements easily and is totally customizable.

Open Source framework designed to build easily Web 2.0 applications, based on a "Client/Server" principle, using J2EE (Servlet, JSP, JDBC), lightweight clients and AJAX technology (XML requests via HTTP)

Sarissa is an ECMAScript library acting as a cross-browser wrapper for native XML APIs. It offers various XML related goodies like Document instantiation, XML loading from URLs or strings, XSLT ... [More] transformations, XPath queries etc and comes especially handy for people doing what is lately known as "AJAX" development. [Less]

This project aims to:Deliver unobtrusive standard-compliant (W3C) cross-browser implementation of the XMLHttpRequest 1.0 object Fix ALL browsers quirks observed in their native XMLHttpRequest object ... [More] implementations Enable transparent logging of XMLHttpRequest object activity Browser quirks fixed: Browser Name Problem description All browsers missing static members (UNSENT, OPENED, HEADERS_RECEIVED, LOADING, DONE) Internet Explorer All / Opera All missing EventTarget interface implementation new Internet Explorer missing native XMLHttpRequest object support Internet Explorer 6.0 memory leak caused by onreadystatechange handler (on-page) Internet Explorer 6.0 memory leak caused by onreadystatechange handler (inter-page) Internet Explorer All connections leakage between pages new Internet Explorer All onreadystatechange wrong execution context Gecko All onreadystatechange wrong execution context Internet Explorer All readystatechange OPENED fired twice Gecko All readystatechange OPENED fired twice Gecko All missing readystatechange calls in synchronous requests Gecko All unnecessary readystatechange DONE call when request aborted Gecko All annoying ">parsererror /<" document for invalid XML documents Internet Explorer All empty documents for invalid XML documents Opera 9.x empty documents for invalid XML documents Internet Explorer 6.0 cached document is not checked against modification date (uncomment in source to use) Internet Explorer All responseXML is not properly initialized for application/xxx+xml responses Safari 3.0 sending document created/modified dynamically chunks serializing Internet Explorer All custom Content-Type overridden when sending XML nodes How To Use: ... ... Known issues:implementation doesn't throw errors on accessing status and statusText properties in an inappropriate moment of time Links to online resourcesXMLHttpRequest object implementation explained [Less]

Enterprise Portal is a web application for small-business in mind. The purpose of application is to let people easily work with customers, vendors, track work within their own company, etc... ... [More] Enterprise Portal is fully extendable and possiblity for connectivity with database through webservices. [Less]

Another aproach of combining existed AJAX frameworks under single Application Markup Language. WAML - Web Application Markup Language. WAML allows you to define your web application appearance and ... [More] functionality by using simple XML like syntax mixed with HTML. The idea behind WAML is to simplify application functionality definition and provide flexible access to UI objects, data and communication services. WAML functionality build on top of existed AJAX frameworks available for public use. [Less]

PurposeTo handle the concurrent connections needed for comet (server to client push) interaction in AJAX applications by queuing and sending messages to client browsers. Concept cometbox ... [More] cometbox is an application written in C#. Console, MS.NET and mono compatible. Maybe someday C or C++ but not for now. Runs on the server. Queues messages for clients. Server Side Your choice of server side language. I personally use PHP and will refer to to this part as PHP. User\Browser The users choice of standard XMLHttpRequest capable web browser. Firefox, IE6, IE7, Safari. Maybe others, I'm not sure yet. Uses javascript and a hefty dose of creativity. (1) An HTTP connection made from the browser via XMLHttpRequest. cometbox accepts the connection and holds it until the browser breaks it off. Upon connection, it sends any pending messages. When cometbox receives a message for the connection from PHP, it sends it through the held connection. Sends the messages in the form of a JSON array. (2) A short life span connection from PHP that sends data to cometbox's queue. Uses XML formated messages. PartsIn order of development importance: Application Core application, in Mono C#. PHP Class Class using PHP sockets to connect to the server app. Uses curl if installed, or fopen otherwise. Javascript Class Class to abstract interaction with the server. Should handle browser quirks that pop up so that theres no hassle to use it. PHP Module More ideal than a PHP class using sockets but requires more knowledge that I have at this point. Why?My main reason is PHP sucks for comet but that is its only real lack for use as an AJAX platform. (Note: This application would be potentially usable with ANY server side application.) To host comet you must have a connection open per active client. In PHP that would mean one loading page per user at all times, at 2-3mb per process this adds up very rapidly. What is Comet?In short comet is a method using only javascript and the http protocol to allow a server to send data to the client without it being requested. Traditionally data could only be given to a browser when requested by that browser. This led to frequent polling of the server which causes high requests as well as slow actual response time. Comet utilizes the XMLHttpRequest to connect to a server side resource that holds the connection open and sends down data as it is received by the server in chunks. This allows for low latency server to client push without resource eating polling. [Less]

With it you can split your class in files for each method and load just the ones you need.