I decided to re-engineer it from the ground up. JPolite V2 is then a complete re-design from the ground up with nothing from V1 except for the look & feel. The code structure is much clearer which makes it easier for customization, as well as integration with other jQuery plugins.

A new feature that is now being tested with JPolite is called XDO (XML Data Object), which currently supports JSON objects only. The whole idea is based on some discussion around “Thin Server Architecture” and REST architecture style, that a browser client first construct the foundation of a web app with STATIC content (HTML, CSS and JavaScript) from a web server, and then exchange only DATA (XML, JSON, TXT) with the application server, which relieves the server from the burden of generating HTML markup. This feature is still experimental with lots enhancements expected.

# Client program

from socket import *

# Set the socket parameters
host = "localhost"
port = 21567
buf = 1024
addr = (host,port)

# Create socket
UDPSock = socket(AF_INET,SOCK_DGRAM)

def_msg = "===Enter message to send to server===";
print "n",def_msg

# Send messages
while (1):
	data = raw_input('>> ')
	if not data:
		break
	else:
		if(UDPSock.sendto(data,addr)):
			print "Sending message '",data,"'....."

# Close socket
UDPSock.close()

$('<ul><li><span class="library" /></li></ul>')
    .items([
        {library:'Prototype'},
        {library:'jQuery'},
        {library:'Dojo'},
        {library:'MooTools'}
    ])
    .chain();

Chain.js isn’t just bind data automatically to your HTML, but it also maintains and manages your data/items.

var data = {first:'Stephen', last:'Hawking'};
 
// Add one item
$('#persons').items('add', data);
 
// Remove item
$('#persons').items('remove', data);

There are actually 3 protocols and 2 APIs that are used in Wave:

• Federation (XMPP)
• The robot protocol (JSONRPC)
• The gadget API (OpenSocial)
• The wave embed API (Javascript)
• The client-server protocol (As defined by GWT)

The last one in that list is really nothing that needs to be, or will probably ever be documented, it is generated by GWT and when you build your own Wave client you will need to define how it talks to your Wave server. The rest of the protocols and APIs are based on existing technologies.

You need to tell subversion what mime-type to use. Just use the command:

svn propset svn:mime-type 'text/html' FILENAME

or

svn propset svn:mime-type 'image/jpeg' FILENAME

For more info: http://svnbook.red-bean.com/en/1.4/svn.advanced.props.file-portability.html#svn.advanced.props.special.mime-type

It's also possible to configure your Subversion client to automatically set
each file's mime-type. For example, by modifying ~/.subversion/config to resemble

[miscellany]
enable-auto-props = yes

[auto-props]
*.html = svn:mime-type=text/html

For more info: http://svnbook.red-bean.com/en/1.1/ch07.html#svn-ch-7-sect-1.3.2 

Username:  	 joe.gregorio
Type the characters you see in the picture below.


Letters are not case-sensitive
Project ownership: 	feedvalidator
robaccia
mimeparse
httplib2
uri-templates
atompub-mulitpart-spec