mirror of https://github.com/apache/activemq.git
Remove the duplicate doctype declarations that are preventing these files from correctly validating.
git-svn-id: https://svn.apache.org/repos/asf/activemq/trunk@1387518 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
parent
b13c8c1e4b
commit
aa5a625a61
|
@ -15,13 +15,6 @@
|
|||
limitations under the License.
|
||||
-->
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||||
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
||||
<html>
|
||||
<head>
|
||||
|
@ -35,30 +28,30 @@
|
|||
@import url(/admin/styles/prettify.css);
|
||||
</style>
|
||||
|
||||
<!--<script type="text/javascript" src="js/prototype.js"></script>-->
|
||||
<!--<script type="text/javascript" src="js/amq_prototype_adapter.js"></script>-->
|
||||
<script type="text/javascript" src="js/jquery-1.4.2.min.js"></script>
|
||||
<script type="text/javascript" src="js/amq_jquery_adapter.js"></script>
|
||||
<!--<script type="text/javascript" src="js/prototype.js"></script>-->
|
||||
<!--<script type="text/javascript" src="js/amq_prototype_adapter.js"></script>-->
|
||||
<script type="text/javascript" src="js/jquery-1.4.2.min.js"></script>
|
||||
<script type="text/javascript" src="js/amq_jquery_adapter.js"></script>
|
||||
|
||||
<script type="text/javascript" src="js/amq.js"></script>
|
||||
<script type="text/javascript" src="js/chat.js"></script>
|
||||
<script type="text/javascript">
|
||||
<script type="text/javascript" src="js/amq.js"></script>
|
||||
<script type="text/javascript" src="js/chat.js"></script>
|
||||
<script type="text/javascript">
|
||||
|
||||
// Note, normally you wouldn't just add an onload function in this
|
||||
// manner. In fact, you typically want to fire this method on the
|
||||
// document.onready event, however this type of functionality is verbose
|
||||
// and best left to the domain of your favorite js library.
|
||||
//
|
||||
// For example, in jQuery the following onload would be replaced with:
|
||||
// jQuery(function() {
|
||||
// org.activemq.Amq.init({ uri: 'amq' });
|
||||
// org.activemq.Chat.init();
|
||||
// }
|
||||
window.onload = function() {
|
||||
org.activemq.Amq.init({ uri: 'amq', logging: true, timeout: 45, clientId:(new Date()).getTime().toString() });
|
||||
org.activemq.Chat.init();
|
||||
};
|
||||
</script>
|
||||
// Note, normally you wouldn't just add an onload function in this
|
||||
// manner. In fact, you typically want to fire this method on the
|
||||
// document.onready event, however this type of functionality is verbose
|
||||
// and best left to the domain of your favorite js library.
|
||||
//
|
||||
// For example, in jQuery the following onload would be replaced with:
|
||||
// jQuery(function() {
|
||||
// org.activemq.Amq.init({ uri: 'amq' });
|
||||
// org.activemq.Chat.init();
|
||||
// }
|
||||
window.onload = function() {
|
||||
org.activemq.Amq.init({ uri: 'amq', logging: true, timeout: 45, clientId:(new Date()).getTime().toString() });
|
||||
org.activemq.Chat.init();
|
||||
};
|
||||
</script>
|
||||
|
||||
</head>
|
||||
|
||||
|
@ -111,59 +104,59 @@
|
|||
<p>Welcome to the Ajax chat example</p>
|
||||
|
||||
<div id="chatroom">
|
||||
<div id="chat"></div>
|
||||
<div id="chat"></div>
|
||||
|
||||
<div id="members"></div>
|
||||
<div id="members"></div>
|
||||
|
||||
<div id="input">
|
||||
<div id="join" class="hidden">
|
||||
Username:
|
||||
<input id="username" type="text"/>
|
||||
<button id="joinB">Join</button>
|
||||
</div>
|
||||
<div id="joined" class="hidden">
|
||||
Chat:
|
||||
<input id="phrase" type="text" />
|
||||
<button id="sendB">Send</button>
|
||||
<button id="leaveB">Leave</button>
|
||||
</div>
|
||||
</div>
|
||||
<div id="input">
|
||||
<div id="join" class="hidden">
|
||||
Username:
|
||||
<input id="username" type="text"/>
|
||||
<button id="joinB">Join</button>
|
||||
</div>
|
||||
<div id="joined" class="hidden">
|
||||
Chat:
|
||||
<input id="phrase" type="text" />
|
||||
<button id="sendB">Send</button>
|
||||
<button id="leaveB">Leave</button>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<p>
|
||||
This Chat example creates an ActiveMQ broker using the configuration
|
||||
information found in the <code>web.xml</code> file. There isn't much there.
|
||||
Just a name-value parameter named <code>org.apache.activemq.brokerURL</code>
|
||||
is assigned a value of <code>vm://localhost?broker.persistent=false</code>.
|
||||
This is enough however to lazy-initialize the broker when it is needed.
|
||||
This Chat example creates an ActiveMQ broker using the configuration
|
||||
information found in the <code>web.xml</code> file. There isn't much there.
|
||||
Just a name-value parameter named <code>org.apache.activemq.brokerURL</code>
|
||||
is assigned a value of <code>vm://localhost?broker.persistent=false</code>.
|
||||
This is enough however to lazy-initialize the broker when it is needed.
|
||||
</p>
|
||||
<p>
|
||||
The client leverages a javascript library <code>amq.js</code> to perform all
|
||||
of the JMS-related client side code. This involves establishing a
|
||||
communication pipeline to the JMS server. This pipeline uses a long-poll
|
||||
connection to the server. All JMS communication will be received down this
|
||||
pipe, and when the JMS server has no traffic to send, this pipeline will
|
||||
patiently wait until there is new traffic or until it times out. If a
|
||||
timeout does occur, the connection will reconnect to the server for another
|
||||
round. (Of course you will want/need to use a server that supports
|
||||
continuations in order for this to scale beyond a few hundred clients.)
|
||||
The client leverages a javascript library <code>amq.js</code> to perform all
|
||||
of the JMS-related client side code. This involves establishing a
|
||||
communication pipeline to the JMS server. This pipeline uses a long-poll
|
||||
connection to the server. All JMS communication will be received down this
|
||||
pipe, and when the JMS server has no traffic to send, this pipeline will
|
||||
patiently wait until there is new traffic or until it times out. If a
|
||||
timeout does occur, the connection will reconnect to the server for another
|
||||
round. (Of course you will want/need to use a server that supports
|
||||
continuations in order for this to scale beyond a few hundred clients.)
|
||||
</p>
|
||||
<p>
|
||||
The <code>chat.js</code> file contains the script to respond to the UI
|
||||
interactions. It also talks to the <code>amq.js</code> file to send messages
|
||||
and provides a message handler that will respond to incoming JMS messages.
|
||||
The <code>chat.js</code> file contains the script to respond to the UI
|
||||
interactions. It also talks to the <code>amq.js</code> file to send messages
|
||||
and provides a message handler that will respond to incoming JMS messages.
|
||||
</p>
|
||||
<p>
|
||||
There is no server-side state in this application. The client sets up a JMS
|
||||
Topic on the server and attaches itself as a listener to this topic. From
|
||||
that point, all messages that are sent to the topic are received by each
|
||||
listener. Even the list of members in the chat room are the result of
|
||||
clients replying to a ping request.
|
||||
There is no server-side state in this application. The client sets up a JMS
|
||||
Topic on the server and attaches itself as a listener to this topic. From
|
||||
that point, all messages that are sent to the topic are received by each
|
||||
listener. Even the list of members in the chat room are the result of
|
||||
clients replying to a ping request.
|
||||
</p>
|
||||
<p>
|
||||
Please note that <code>amq.js</code> has been refactored to allow AJAX calls
|
||||
to be made using any javascript library. Example adapter classes for <a href="http://jquery.com/">jQuery</a>
|
||||
and <a href="http://www.prototypejs.org/">Prototype</a> have been provided.
|
||||
Please note that <code>amq.js</code> has been refactored to allow AJAX calls
|
||||
to be made using any javascript library. Example adapter classes for <a href="http://jquery.com/">jQuery</a>
|
||||
and <a href="http://www.prototypejs.org/">Prototype</a> have been provided.
|
||||
</p>
|
||||
|
||||
|
||||
|
|
|
@ -15,13 +15,6 @@
|
|||
limitations under the License.
|
||||
-->
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||||
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
||||
<html>
|
||||
<head>
|
||||
|
|
|
@ -15,13 +15,6 @@
|
|||
limitations under the License.
|
||||
-->
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||||
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
||||
<html>
|
||||
<head>
|
||||
|
|
Loading…
Reference in New Issue