Welcome to The TCP/IP Guide!
Service Registry Vs. UDDI registry
A lot of registry vendors use the terms "service registry" or "SOA registry" to indicate that the registry offers more features than what are the minumum requirements to conform to the UDDI spec (what I call "vanilla UDDI".) The UDDI spec defines a standard data model (comprising four primary entities: businessEntity, businessService, bindingTemplate, and tModel) and a set of APIs for accessing the registry (Inquiry, Publish, Security, Custody, Replication, Subscription, and Value Set). The data model is inherently extensible (you can capture almost any type of information using tModels), but because of this extensibility, it really helps if you have high-level tooling that abstracts the relationships and makes navigation more intuitive. Without high-level tooling, most users will find UDDI incomprehensible. Note that UDDI is not just for web services.
MySecureShell SFTP-Server - Index
Getting Started with WebRTC
WebRTC is a new front in the long war for an open and unencumbered web. Brendan Eich, inventor of JavaScript Real-time communication without plugins Imagine a world where your phone, TV and computer could all communicate on a common platform. Imagine it was easy to add video chat and peer-to-peer data sharing to your web application. Want to try it out? Open apprtc.appspot.com in Chrome, Opera or Firefox. There is a walkthrough of this application later in this article. Quick start Haven't got time to read this article, or just want code? Get an overview of WebRTC from the Google I/O presentation (the slides are here): If you haven't used getUserMedia, take a look at the HTML5 Rocks article on the subject, and view the source for the simple example at simpl.info/gum. Alternatively, jump straight into our WebRTC codelab: a step-by-step guide that explains how to build a complete video chat app, including a simple signaling server. A very short history of WebRTC Where are we now? Constraints
CS402: Computer Communications and Networks
The Internet has become one of the most important components of our life. We browse the Web, check e-mails, make VoIP phone calls, and have video conferences via computers. All of these applications are made possible by networking computers together, and this complex network of computers is usually referred to as the Internet. This course is designed to give you a clear understanding of how networks, from in-home local area networks, or LANS, to the massive and global Internet, are built and how they allow us to use computers to share information and communicate with one another. Unit 1 introduces you to an explanation of what computer networks are as well as to some basic terminology fundamental to understanding computer networks. The rest of the course implements a top-down approach to teach you the details about each layer and the relevant protocols used in computer networks. This course is designed to align with a Thomas Edison State College TECEP examination.
Ports Required for Various Services/Applications
Ports Required for Various Services/Applications Copyright © 2001-2013 Thomas M. Eastep Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover, and with no Back-Cover Texts. Abstract In addition to those applications described in the /etc/shorewall/rules documentation, here are some other services/applications that you may need to configure your firewall to accommodate. Caution This article applies to Shorewall 3.0 and later. Note Shorewall distribution contains a library of user-defined macros that allow for easily allowing or blocking a particular application. ls /usr/share/shorewall/macro.* for the list of macros in your distribution. #ACTION SOURCE DESTINATION DNS(ACCEPT) dmz net In the rules that are shown in this document, the ACTION is shown as ACCEPT. You would code your rule as follows:
4: Change the default sshd port
The changes induced with Tiger seem to be causing great pain to many in regards to sshd and changing the default port. A hint is already on file for doing this in 10.3, which even so, seems to have caused a bit of a stir. To note -- I'm not endorsing security through obscurity, but this is still a useful exercise and one that can reduce the number of people probing the standard ssh port. In 10.4, the mechanism for launching sshd changed from using xinetd to launchd. This dramatically changed how sshd is launched, what ports are listened to, etc. Logically, you would think you could just edit /etc/sshd_config and be done with it. In general, in most on-demand plists for launchd, a key can be found called SockServiceName. <key>SockServiceName</key><string>ssh</string> No, it doesn't list a port number; it lists a service name that is looked up by the getAddrInfo() function call. ssh2 10022/udp ssh2 10022/tcp <key>SockServiceName</key><string>ssh2</string>
Explicit Congestion Notification
Explicit Congestion Notification (ECN) is an extension to the Internet Protocol and to the Transmission Control Protocol and is defined in RFC 3168 (2001). ECN allows end-to-end notification of network congestion without dropping packets. ECN is an optional feature that may be used between two ECN-enabled endpoints when the underlying network infrastructure also supports it. Conventionally, TCP/IP networks signal congestion by dropping packets. Rather than responding properly or ignoring the bits, some outdated or faulty network equipment has historically dropped or mangled packets that have ECN bits set.[1][2][3] As of 2015[update], measurements suggest that the fraction of web servers on the public Internet for which setting ECN prevents network connections has been reduced to less than 1%.[4] Operation[edit] ECN requires specific support at the Internet layer and the transport layer for the following reasons: Operation of ECN with IP[edit] Operation of ECN with TCP[edit] Unix-like[edit]
OpenSSO Enterprise - Overview
Oracle acquired Sun Microsystems in 2010, and since that time Oracle's hardware and software engineers have worked side-by-side to build fully integrated systems and optimized solutions designed to achieve performance levels that are unmatched in the industry. Early examples include the Oracle Exadata Database Machine X2-8, and the first Oracle Exalogic Elastic Cloud, both introduced in late 2010. During 2011, Oracle introduced the SPARC SuperCluster T4-4, a general-purpose, engineered system with Oracle Solaris that delivered record-breaking performance on a series of enterprise benchmarks. Oracle's SPARC-based systems are some of the most scalable, reliable, and secure products available today. Sun's prized software portfolio has continued to develop as well, with new releases of Oracle Solaris, MySQL, and the recent introduction of Java 7.
