× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




No, i haven't done anything with JXTA. Just interested.

Date: Fri, 18 Jul 2008 09:10:50 -0500
From: aaronbartell@xxxxxxxxx
To: web400@xxxxxxxxxxxx
Subject: Re: [WEB400] The "Presentation" Layer

Oh man, that explanation (which I haven't heard described before) really has
the wheels turning in my head. Kinda makes a guy rethink some ideas I had
formalized.

Have you done any JXTA implementations? And if so what was the scenario?

Aaron Bartell
http://mowyourlawn.com


On Fri, Jul 18, 2008 at 8:37 AM, john e <jacobus1968@xxxxxxxxxxx> wrote:


P2P is when the two sides on a connection can be either a client, a server,
or both. Specifically, client/server is an architectural approach which is
simple, robust, and scalable (i never said client/server is a bad thing).

By designating a specific role (client or server) to each side it makes
implementing a scalable and robust distributed app simple. A client always
initiates a request to the server, and a server simply processes requests. A
client also typically knows the address of the server wher to send the
requests to.

If you have simply TCP/IP, you actually have a peer-to-peer network. Each
program can connect to any other program and take on whichever role. But
distributing code over different processes which are "peers" (i.e. they are
equal) is more difficult to implement.

You can say that APPN is peer-to-peer and TCP/IP is not, because APPN
implements additional functionality that is specifically for peer-to-peer
networking such as discovery of neighbor peers. In TCP/IP you have to
implement this yourself with e.g. UDP. In APPN, the LU6.2 logical unit is
the "peer" on the network. LU6.2 supports different protocols for dealing
with peer-to-peer networking.

A green-screen terminal is also a peer in the network, but in practice it
acts more as a server, and the program running on the host is the client.
E.g. the program requests the terminal to display a format. So most of the
time a terminal takes on the server role. However, at first, when logging
into the system, a terminal initiates a session and has the client role.


--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.


_________________________________________________________________
De mooiste afbeeldingen van Angelina Jolie vind je met Live Search
http://search.live.com/images/results.aspx?q=angelina%20jolie&FORM=MIINTM

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.