[xSocket-develop] Comet bayeux

[<bb...@ke...>]

<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-ansi-language:EN-GB;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:"Times New Roman";
	mso-ansi-language:EN-GB;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 77.95pt 72.0pt 77.95pt;
	mso-header-margin:35.4pt;
	mso-footer-margin:35.4pt;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->


Greetings,

 

I came across the xSocket via this
article:
http://www.javaworld.com/javaworld/jw-03-2008/jw-03-asynchhttp.html?page=1

 

I have been working on a bayeux java
implementation (as a part of my masters dissertation) and I took a look at your
SVN repository where you have a bayeux implementation going. Would you say that
your bayeux implementation is fairly mature? I would like to get a nonblocking
java bayeux client working, how much work needs to be done on yours? Maybe I
can expand on it and implement what is left? 

 

Why are all of the classes in
org.xsocket.bayeux.http defined as "final class.."? I'm not able to
instansiate any of those classes unless my class is in the same package. Is
that the idea?

 

Regards,

- Bjarki Bjorgulfsson