User: hiram
Date: 01/01/26 04:44:57
Added: business jboss-jbossmq.html
Log:
no message
Revision Changes Path
1.1 newsite/business/jboss-jbossmq.html
Index: jboss-jbossmq.html
===================================================================
<html>
<head>
<meta http-equiv="content-type" content="text/html;charset=iso-8859-1">
<meta name="generator" content="Adobe GoLive 4">
<link rel="stylesheet" type="text/css" href="main.css" >
</head>
<body marginwidth="0" marginheight="0" onload="">
<table border="0" cellpadding="0" cellspacing="3">
<tr>
<td width="600" valign="top">
<table border="0" cellpadding="2"
cellspacing="0">
<tr>
<td class="pageheader"><b>JBoss/jBossMQ</b></td>
</tr>
<tr>
<td
class="newsheader"><b>JBossMQ a JMS implementation</b></td>
</tr>
<tr>
<td class="newsbody"><font face="Myriad Web,Arial">
JBossMQ (originally spyderMQ) was released
in April 2000 as the first free implementation of the Java Messaging
Service (TM) (JMS) specification. Based on the 1.0.2 JMS specification,
JBossMQ is a clean room, pure java implementation.</font>
<p><font face="Myriad Web,Arial">
It is not uncommon for the Web to
fail, for nodes to fail, and for communications in general to fail.
Therefore, distributed applications cannot always depend on a
synchronous
messaging model to reliably deliver notifications. That's why, in
addition to synchronous messaging, JMS also provides an asynchronous
messaging model that implements the Publish/Subscribe design pattern.
A Publish/Subscribe model is critical for successful collaboration
between the various participants of a distributed, e-business
application.
We believe JMS, through our JBossMQ component, plays a central
role in the J2EE-based "Web operating system" provided by the
jBoss.</font></p>
<p><font face="Myriad Web,Arial">JBossMQ was originaly started
under the leadership
of <b>Norbert Lataille</b>, at that time called spyderMQ.
Since then, spyderMQ
was renamed to JBossMQ and is being lead by <b>Hiram
Chirino</b>. Development
of JBossMQ is progressing fast and will soon reach 1.0. All
JMS 1.0.2 features
have been implemented and the 1.0 release is eagerly awaited.
This is alpha software,
but remarquably stable.</font>
<p>
</td>
</tr>
<tr>
<td
class="newsheader"><b>Features</b></td>
</tr>
<tr>
<td class="newsbody">
<font face="Myriad Web,Arial">
<p>
Every aspect of the JMS 1.0.2
spec has been implemented such as:
<ul>
<li>Both
point-to-point and publish-subscribe style messaging
<li>Durable subscribers
<li>JMS Application
Server Facilities
<li>Ability to participate
in in global units of work coordinated by a TM.
</ul>
<p>
Serveral diffrent kinds of
message transport/invocation layers available.
<ul>
<li>RMI - RMI based
invocation layer
<li>OIL - Stands for
Optimized Invocation Layer. This layer uses custom TCP/IP
sockets to
obtain good network performance and small memory footprint.
<li>UIL - For client
applications that can not accept network connections
originating
from the server.
</ul>
<p>
</font>
</td>
</tr>
<tr>
<td
class="newsheader"><b>Mailing lists</b></td>
</tr>
<tr>
<td class="newsbody"><font
face="Myriad Web,Arial">
Join us now! Come on board of
the JBossMQ project, the
real messaging infrastructure
of the web. You can find
our mailing list <a
href="lists.html">here.</a></font>
<p>
</td>
</tr>
<tr>
<td
class="newsheader"><b>Distribution and CVS</b></td>
</tr>
<tr>
<td class="newsbody"><font face="Myriad Web,Arial">JBossMQ is
distributed as part of jBoss/Server.</font>
<p><font face="Myriad Web,Arial">CVS module is <a
href="cvs.html">jbossmq</a></font></td>
</tr>
</table>
</td>
</tr>
<tr>
<td width="600"></td>
</tr>
</table>
</body>
</html>
- [jBoss-Dev] CVS update: newsite/business jboss-jboss... jBoss CVS Development
- [jBoss-Dev] CVS update: newsite/business jboss-... jBoss CVS Development
