Skip to main content

Some questions..

2 replies [Last post]
talthibios84
Offline
Joined: 2007-08-08

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
talthibios84
Offline
Joined: 2007-08-08

Dear Ashgar,

First of all thanks for your reply.

http://nms.lcs.mit.edu/papers/ins-sosp99.pdf

This a link for a paper with some basics for INS that I am trying to study, although you might already find it. But when I find out more about INS, I'll be glad to let you know!!

Best regards,
Kostas

asghar
Offline
Joined: 2005-07-26

Hello!

Same questions, I got, as I begun t o learn about JXTA!
I don’t know, what [b]INS[/b] is?
Can you provide me a link to read about?

The structure (and scoping of audiences) of [b]OSI 7-layer model[/b] and the [b]3-layer model[/b] (Core, Service, Application), mentioned in Programmer’s Guide of [b]platform standard impl.[/b] (for [b]Java[/b]) are fully different.
While keeping in mind, that meaning of and border between service and application layers are a matter of individual interpretation, the customized version of 3-layer model is encountered in other service oriented env. like Bluetooth, whereby there the layers have different identifier once again!

JXTA, at its essence is a (relatively) small collection of protocols ([b]JXTA protocol stack[/b]), acting as basic building blocks for pure P2P or hybrid-modeled applications.

We should remember that platform standard impl. is much more than the sum of those functionalities, specified by JXTA Spec. Ver 2.0.

Referred to OSI-model, (let say) JXTA protocol stack belongs to layers above IP-layer ([b]3. layer[/b]), or to [b]application layer[/b] of the simplified OSI Model, used in TCP/IP literature (1. Network access, 2. Internet, 3. Transport, 4. Application), even JXTA protocol stack naturally relates to low-level oriented matters. It extends the standard transport protocols of TCP/ IP protocol stack [b]AND[/b] is open to other transport protocols, to meet the requirements of modern networked applications (and the JXTA very own applications, incl. some upcoming killer-applications).

I like to recommend the technical writers of our community to refer often to OSI-model, when describing the layered structure of JXTA protocol stack. That leads to easier understanding of JXTA.

OSI-model is well-known to almost developers of networked software programs and to network administrators too.

Asghar