From de8ffc8a584734066cb652b17867cd591782afa5 Mon Sep 17 00:00:00 2001 From: "nor..67" Date: Sun, 25 Sep 2011 00:04:39 +0000 Subject: [PATCH] - remove spidermonkey page from javahelp git-svn-id: https://jmonkeyengine.googlecode.com/svn/trunk@8295 75d07b2b-3a1a-0410-a2c5-0572b91ccdca --- .../com/jme3/gde/core/docs/spidermonkey.html | 114 ------------------ 1 file changed, 114 deletions(-) delete mode 100644 sdk/jme3-core/javahelp/com/jme3/gde/core/docs/spidermonkey.html diff --git a/sdk/jme3-core/javahelp/com/jme3/gde/core/docs/spidermonkey.html b/sdk/jme3-core/javahelp/com/jme3/gde/core/docs/spidermonkey.html deleted file mode 100644 index 416c7e37e..000000000 --- a/sdk/jme3-core/javahelp/com/jme3/gde/core/docs/spidermonkey.html +++ /dev/null @@ -1,114 +0,0 @@ - -

SpiderMonkey

-
- -

-SpiderMonkey is a high performance Java networking engine, aiming to provide game developers a stable and efficient networking system. It's also perfectly capable of doing anything other than game networking. SpiderMonkey is part of jME3 and can be found in the src/networking directory. -

- -

-Author: Lars 'Levia' Wesselius
- -License:
- -Blog:
- -Forum:
- -
- -

- -

-A tutorial trail can be found below, and below that all different aspects of SpiderMonkey are explained. These tutorials are to be updated upon SVN HEAD, so if new features are added in SVN, you should tutorials arriving of them soon. - -

- -
- -

Tutorial trail

-
-
    -
  1. Connections
    -
    2. -
  2. Sending and receiving messages
    -
    3. -
  3. Serialization
    -
    4. -
  4. Compression
    -
    5. -
  5. Services
    -
    6. -
  6. Streaming
    -
    7. -
- -
- -

Explanation of SpiderMonkey's inner workings

-
- -
- -

Connection protocols

-
- -

-SpiderMonkey supports both TCP and UDP, and is also extendable to provide others. Possible future protocols may be RUDP, UDP Lite, and SCTP. SCTP will be added in Java 7, and will therefore probably added to SpiderMonkey after it's released. Please note that the language level of SpiderMonkey is 1.5, so it will definitely not be part of the standard API for a few years. -

- -
- -

Clients

-
- -

-SpiderMonkey creates two connections by default. A TCP connection for a reliable connection, and an UDP 'connection' 1) for fast message handling. A problem arises here: these two connections mean that even though there are two connections, there's only one client to represent both the connections. In SpiderMonkey you don't have to worry about that. The server has a client manager which deals with this problem. Upon connecting, clients have to send a ClientRegistration message to link their TCP and UDP connections together. Upon receiving those two messages, server combines the clients into one, and provides this client to you. This means you can call both TCP and UDP methods on the client. If you still want to receive the 'local' client of a connection, you can do so by calling the appropriate messages in the Server class. - -

- -
- -

Serializing

-
- -

-Serializing is an aspect that received a lot of attention. I wanted it to be simple for people to register their own messages, but also be able to register serializers for their own object types. The system works by registering classes to serializers. Generally, a serializer does not exist without a class it can serialize - simply because it doesn't have to: Why have a serializer when there's nothing to serialize. A lot of work has been put into making it as efficient as possible. What can be left out, is left out, and what can optimized, is optimized. -

- -
- -
Field serializer
-
- -

-The default serializer requires some explanation. This serializer serializes all classes that have no (registered) serializer. The field serializer works by saving all fields internally, so it can access them on serialization faster. The fields are taken, and their types are checked. They are put through a serializer again (which serializer depends, of course, on the data type). Then they are ready to be written to the buffer. As you can tell, this is quite a simple serializer, and should be used if your message don't require extra attention. See this tutorial if you want to know how to register your own messages or serializers. - -

- -
- -

Service system

-
- -

-The service system is in fact a tiny system. It's meant to solve a small, but annoying problem. Imagine you have SpiderMonkey as your networking library, and other people have made extra's for it. Excellent, of course, but they may all require different initialization! Perhaps you have to instantiate one yourself by using new, or maybe another works by calling a factory method; the service system exists to avoid that problem. All extras should use this system. Please see the service tutorial on how to use this system. - -

- -
- -

Compression

-
- -

-By default SpiderMonkey supports compressing messages. It's been made to where you have complete freedom over what messages you wish to compress. See this tutorial on how to use these special messages. - -

- -
-
-
1) -UDP is connectionless
-
-

view online version

\ No newline at end of file