Kaazing Gateway 8.12 (Default branch)

Tags

default, gateway, software releases

Special Forums News, Links, Events and Announcements Software Releases - RSS News Kaazing Gateway 8.12 (Default branch)

12-11-2008

Registered User

26,240, 27

Join Date: Sep 2000

Last Activity: 1 August 2008, 3:09 PM EDT

Posts: 26,240

Thanks Given: 0

Thanked 27 Times in 26 Posts

Kaazing Gateway 8.12 (Default branch)

Kaazing Gateway is an HTML 5 WebSocket server thatprovides full-duplex communication from thebrowser to any TCP-based back-end service (such asJMS, JMX, IMAP, Jabber, etc.), enabling developersto code directly against back-end services using"pure" JavaScript without having to implementcomplex server-side procedures to bridge variousprotocols to the browser over HTTP.License: OSI ApprovedChanges:
This release adds support for HTML 5 server-sent events and broadcast notification. It supports HTML 5 postMessage. It introduces W3C access control security. It provides group chat support for XMPP. It contains a JMS-STOMP adapter.

More...

Linux Bot

View Public Profile for Linux Bot

Find all posts by Linux Bot

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

Inconsistency between RedHat 6.5 global gateway and single gateway leads to loss of default gateway

Dear friends I use RedHat 6.5, which sets the gateway in the configuration file / etc / sysconfig / network as GATEWAY = 192.168.1.26, and the gateway in the configuration file / etc / sysconfig / network-scripts / ifcfg-eth11 as GATEWAY = 192.168.1.256. The two gateways are different....

LEARN ABOUT DEBIAN

poe::component::jabber::j14

POE::Component::Jabber::J14(3pm)			User Contributed Perl Documentation			  POE::Component::Jabber::J14(3pm)

NAME

       POE::Component::Jabber::J14 - connect to the jabberd14 router as a service

SYNOPSIS

       PCJ::J14 is a Protocol implementation that connects as a service to a jabberd14 server.

DESCRIPTION

       PCJ::J14 authenticates with the server backend using the method outlined in XEP-114 (Jabber Component Protocol)
       [http://www.xmpp.org/extensions/xep-0114.html]

METHODS

       Please see PCJ::Protocol for what methods this class supports.

EVENTS

       Listed below are the exported events that end up in PCJ's main session:

       set_auth
	 This event constructs and sends the <handshake/> element for authentication.

       init_input_handler
	 This is out main entry point that PCJ uses to send us all of the input. It handles the authentication response.

NOTES AND BUGS

       This only implements the jabber:component:accept namespace (ie. the component initiates the connection to the server).

       Also be aware that before this protocol was documented as an XEP, it was widely implemented with loose rules. I conform to this document.
       If there is a problem with the implementation against older server implementations, let me know.

       The underlying backend has changed this release to now use a new Node implementation based on XML::LibXML::Element. Please see
       POE::Filter::XML::Node documentation for the relevant API changes.

AUTHOR

       Copyright (c) 2003-2009 Nicholas Perez. Distributed under the GPL.

perl v5.12.4							    2011-08-09					  POE::Component::Jabber::J14(3pm)

Software Releases - RSS News