wsdl:schema

http://www.whitemesa.net/soap12WSDL.htm

webservice:axis

http://www.sosnoski.com/presents/java-xml/axis/axis/siframes.html

http://www.apache.org/~haddadc/presentations/AxisWSEdgeEast2004.pdf

jndi

If I had written the code like this:Context c = newInitialContext();
DataSource ds = c.lookup("java:comp/env/jdbc/Bank");
the container would look up 'jdbc/Bank' in the EJB's local namespace. Now using a resource reference, we can say that in this EJB, the data source known to the container as BankDB is referred to locally as jdbc/Bank. In this example 'jdbc/Bank' is the 'coded name.' In other words, using resource references allows us to resolve incorrect or unknown resource names at deployment time, without modifying the code.

So when we specify a name that begins with java:comp/env, the JNDI implementation is being told to make a lookup in the part of the name/directory that is dedicated to that particular EJB.

Starting with EJB 1.1, all beans have a default JNDI context called the enterprise naming context. The default context exists in the namespace called java:comp/env (based on a URL context for the java: URL scheme) and its subdirectories. When a bean is deployed, any beans it uses are mapped into the java:comp/env/ejb directory so that the bean references can be obtained at runtime through a simple and consistent use of the JNDI ENC. This eliminates network and implementation specific use of JNDI to obtain bean references. For example, you might use a name such as "java:comp/env/jdbc/myDB" from the initial context to name the myDB database. At the root context of the namespace is a binding with the name "comp", which is reserved for component-related bindings.
In addition, the name "env" is bound to a subtree that is reserved for the component's environment-related bindings, as defined by its deployment descriptor. The J2EE specifications recommend that EJBs be placed under the "ejb" subtree. For example, an EnrollmentCartHome EJB might be named "java:comp/env/ejb/EnrollmentCartHome".

webservice:jax-rpc

http://www.pankaj-k.net/axis4tag/28

linux:kernel

http://www.itcourseware.com/Webpdfs/weboi-intern.pdf

syslog

http://www.cert-in.org.in/guidelines/CISG-2004-03.pdf

log4j

tutorial:http://www-106.ibm.com/developerworks/java/library/j-instlog/

dictionary:telecom

http://www.atis.org/tg2k/

java:classfileeditor

http://classeditor.sourceforge.net/screenshot/index.html

http://jakarta.apache.org/bcel/manual.html

grid:cisco

http://wwwin.cisco.com/alliances/tech_strategies/initiatives/grid/index.shtml

xml:rootnode

http://www.dpawson.co.uk/xsl/sect2/root.html#d7898e13

nachos:berkeley

http://hegel.ittc.ukans.edu/projects/nachos/nachos/nachos.html

webservice:encoding

There are 4 messaging mode:
RPC/Literal(recommended), Document/Literal(recommended)
RPC/Encoded, Document/Encoded.

where X/Y, X is the message style (how to represent it),
Y is encoding. Literal means xml fragement.

RPC messaging style only has one child, the function which
contains its own children for the parameters.

Message flow/pattern: request/response or one-way.
Both RPC & Document supports both flow.
However, it is common for RPC to support request/response.

http://java.sun.com/developer/Books/j2ee/jwsa/JWSA_CH10.pdf

RPC literal example:


RPC/Encoding example:


http://www-106.ibm.com/developerworks/library/ws-jaxrpc1/

windows:ephemeral-port

http://www.jsiinc.com/SUBK/tip5200/rh5249.htm

from 1024 to 5000 with wait_state for 4 mins

http://www.jsiinc.com/SUBN/tip6600/rh6633.htm

thread:sleep-yield

http://saloon.javaranch.com/cgi-bin/ubb/ultimatebb.cgi?ubb=get_topic&f=27&t=001087

yield only yield to other thread in the same VM.
Sleep really sleep

http://hegel.ittc.ukans.edu/projects/nachos/html-source/thread.cc.html

webservice:book

http://java.sun.com/blueprints/guidelines/designing_webservices/html/

http://www.sourcebeat.com/TitleAction.do?id=1
for axis.

http://webservices.xml.com/pub/a/ws/2002/04/24/google.html?page=2

known-port

http://security.ou.edu/ports.htm

beep

http://xml.coverpages.org/beep.html

http://wwwin-eng.cisco.com/Eng/IOS/Graffiti/PRDs/beep-prd.doc

· Beepcore (http://www.beepcore.org/), which provides a “beepcore” software library, available in Java, C, and Tcl flavors.
· CodeFactory (http://www.codefactory.se), which provides RoadRunner, an implementation of the BEEP protocol written in C.

http://www.xml.com/lpt/a/2002/10/16/ends.html

syslog:reliable

http://wwwin-eng.cisco.com/Eng/IOSTech/WWW/Infrastructure/Serviceability/syslog/documents/22

Beep:
http://beepcore.org/prodproj.html

article:
https://www.linux-magazine.com/issue/37/Syslog-NG.pdf

webservice:security

http://www.pankaj-k.net/

proxy:dynamicproxy

why dynamic proxy:
http://www.javaworld.com/javaworld/jw-02-2002/jw-0215-dbcproxy-p3.html

http://www.devx.com/Java/Article/21463/0/page/2

soap:saaj

http://www.javaworld.com/javaworld/jw-09-2003/jw-0912-webservices-p2.html

database:copyrow

insert into myTable (col1,col2)
select * from tablex where Y > 1

windows:name-resolver

http://www.windowsitlibrary.com/Content/172/01/13.html

sequence:

NetBIOS name cache
WINS
Broadcast
LMHOSTS
HOSTS
Domain Name System (DNS)

eclipse:document

http://www.eclipse.org/documentation/pdf/org.eclipse.platform.doc.user_3.0.pdf

crack

http://www.eag.ru/?2=67348

linux:db2

http://www.redbooks.ibm.com/redbooks/pdfs/sg246934.pdf
for using DB2

disk:vertias

http://wwwin-scs.cisco.com/reference/veritas/ug.pdf

linux:networking:ip-tutorial

http://www.kernelnewbies.org/documents/

http://www.kernelnewbies.org/documents/kdoc/kernel-locking.pdf
for kernel locking

source code on web with cross reference
http://lxr.linux.no/source/net/ipv4/ip_forward.c

tutorial on stack
http://www-scf.usc.edu/~rishisin/ngroup/23

windows:winsock:maxsockets

http://www.topjimmy.net/tjs/

The TJPingPro info menu will show the max # of sockets