User:Ornette

Ornette
Name	Ornette
Real Name	jonlin
Date of birth	June, 24th, 1974
Homeland	Taiwan
Role	Thread Archiving
Lot in life	Boozing
Favorite Episode	24'
Favorite Character	Asuka Langley Soryu
Favorite Relationship	N/A
Favorite Angel	Leliel
Favorite Evangelion	N/A

Who Am I

• Co-owner of a software and consulting company, Comet Way, Inc.
• Lead programmer at Comet Way
• System administrator for Comet Way and the local ISP (Pittsburgh) Angstrom, Inc.
• Freelance security consultant
• Various opensource software contributor
• One of the organizers for Summercon, an annual hackers conference held in different places in the U.S (2001 was in Amsterdam)
• Likes to drink Single Malt Scotch Whisky (note: that is not a mispelling)
• Likes to watch anime
• Avid Formula 1 racing fan
• Plays Classical guitar and Jazz, 3 years with the Carnegie Mellon Classical Guitar Ensemble under professor James Ferla
• Hates Microsoft Windows

Evangelion

I've been watching anime since longer than I can remember. Although between 2000 and 2006, I was heavily wrapped up in the MMORPG Everquest so 90% of all of my time awake was spent playing this game, I still managed to sneak in a few series while I was doing other things. It wasn't until 2004 that I finally got around to watching Evangelion. I, in part, avoided it because of the tremendous amount of hype I'd encounter when browsing for recommendations or looking into my next purchase. When I finally gave in and bought a used copy of the Perfect Collection, I was blown away by the layers upon layers of themes and a story that is told in a sparse way but was deceivingly complex. It was the first show that I watched that prompted me to actually read, and later discuss, about in online forums. And that's where it all began.

More

• http://www.tesuji.org/ - Home Page, "tesuji" is a term used in the game of Go meaning "the good move", as in, "That move was the tesuji". In 1998, I was playing a lot of Go and couldn't think of a domain name to use as my personal online presence.
• http://www.cometway.com/ - Company home page
• http://www.summercon.org/ - Summercon home page
• http://ornette.myanimelist.net/ - My MAL page
• http://www.moderndrunkardmagazine.com/ - No comment needed
• http://www.ornettecoleman.com/ - My hero, and namesake

test

This class represents an Internet Protocol (IP) address.

An IP address is either a 32-bit or 128-bit unsigned number used by IP, a lower-level protocol on which protocols like UDP and TCP are built. The IP address architecture is defined by RFC 790: Assigned Numbers, RFC 1918: Address Allocation for Private Internets, RFC 2365: Administratively Scoped IP Multicast, and RFC 2373: IP Version 6 Addressing Architecture. An instance of an InetAddress consists of an IP address and possibly its corresponding host name (depending on whether it is constructed with a host name or whether it has already done reverse host name resolution). Address types

   unicast 	An identifier for a single interface. A packet sent to a unicast address is delivered to the interface identified by that address.

   The Unspecified Address -- Also called anylocal or wildcard address. It must never be assigned to any node. It indicates the absence of an address. One example of its use is as the target of bind, which allows a server to accept a client connection on any interface, in case the server host has multiple interfaces.

   The unspecified address must not be used as the destination address of an IP packet.

   The Loopback Addresses -- This is the address assigned to the loopback interface. Anything sent to this IP address loops around and becomes IP input on the local host. This address is often used when testing a client.
   multicast 	An identifier for a set of interfaces (typically belonging to different nodes). A packet sent to a multicast address is delivered to all interfaces identified by that address.

IP address scope

Link-local addresses are designed to be used for addressing on a single link for purposes such as auto-address configuration, neighbor discovery, or when no routers are present.

Site-local addresses are designed to be used for addressing inside of a site without the need for a global prefix.

Global addresses are unique across the internet. Textual representation of IP addresses The textual representation of an IP address is address family specific.

For IPv4 address format, please refer to Inet4Address#format; For IPv6 address format, please refer to Inet6Address#format. Host Name Resolution Host name-to-IP address resolution is accomplished through the use of a combination of local machine configuration information and network naming services such as the Domain Name System (DNS) and Network Information Service(NIS). The particular naming services(s) being used is by default the local machine configured one. For any host name, its corresponding IP address is returned.

Reverse name resolution means that for any IP address, the host associated with the IP address is returned.

The InetAddress class provides methods to resolve host names to their IP addresses and vice versa. InetAddress Caching The InetAddress class has a cache to store successful as well as unsuccessful host name resolutions.

By default, when a security manager is installed, in order to protect against DNS spoofing attacks, the result of positive host name resolutions are cached forever. When a security manager is not installed, the default behavior is to cache entries for a finite (implementation dependent) period of time. The result of unsuccessful host name resolution is cached for a very short period of time (10 seconds) to improve performance.

If the default behavior is not desired, then a Java security property can be set to a different Time-to-live (TTL) value for positive caching. Likewise, a system admin can configure a different negative caching TTL value when needed.

Two Java security properties control the TTL values used for positive and negative host name resolution caching:

   networkaddress.cache.ttl
       Indicates the caching policy for successful name lookups from the name service. The value is specified as as integer to indicate the number of seconds to cache the successful lookup. The default setting is to cache for an implementation specific period of time.

       A value of -1 indicates "cache forever".

   networkaddress.cache.negative.ttl (default: 10)
       Indicates the caching policy for un-successful name lookups from the name service. The value is specified as as integer to indicate the number of seconds to cache the failure for un-successful lookups.

       A value of 0 indicates "never cache". A value of -1 indicates "cache forever".