Last week, we had the author of TDD for a Shopping Website LiveProject. Friday at 11am Ranch time, Steven Solomon will be hosting a live TDD session just for us. See for the agenda and registration link
Hi, Pls view the following html code: <OBJECT classid=clsid:3CD9-53RT-193Q-2106-OI0C9 codeBase=http://abc.com/applet/cc.cab#Version=0,3,6,7 id=tomm style="CENTER: 0px; TOP: 0px" HIDDEN></OBJECT> <APPLET code=Ty.0 codeBase=http://abc.com/applet/df381/ height="100%" width="100%"> Is the applet and class resided on the remote server and used rmi or cobra to get the remote object? What is cab file? BTW, anyone could recommend a socket programming for java to me? Is Jini relating to network programming and Jxta relating to P2P programming? If I want to build a remote server like the above case, which technology should I deploy? Also, how can I get and keep on update the IP of a client machine which is used dynamic IP? Is it relating to network programming also? Thanks in advance. Andrew
:roll: [ January 07, 2002: Message edited by: Andrew Parker ]
*.cab is a compressed file. If you ever looked into install-CD of Windows 9x, you will find numerous *.cab files that contain drivers and compressed install files. It's still an idea that one day Java will be combined with CORBA to construct Object/Web. One possible way is to enable clients to download Java applets from Internet and the applets use various CORBA services. But now, applets mainly run in a constricted enviroment. It seldom calls rmi, let alone CORBA. Elliot Rusty Harold's book Java Network Programming is very good. I have finished it and learned quite a lot. Jini and Jxta are both related to distributed comoputing. Jxta focuses on peer-to-peer operation while Jini concentrates on the interaction of distributed objects. More information can be found at www.jxta.org and www.sun.com As for the IP address of a client, you can know it by calling Class Socket's method: public InetAddress getInetAddress() If the connection has been closed (but the socket has not been closed), this method returns the formerly connected remote host's InetAddress.
" Veni, vidi, vici "<br />" I came, I saw, I conquered "
Thanks for all of your kind help. I will buy those 2 books to learn the network programming. May I ask you that whether the distributed computing - interaction of distributed objects (Jini) relating to CORBA / RMI? and Jxta focuses on how various devices communicate through P2P? So, Jxta does not relate to distrubuted computing. Regards Andrew
About Jini: Here's the vision: When you walk up to an interaction device that is part of a Jini system, all of its services are as available to you as if they were on your own computer-and services include not only software but hardware devices as well, including disk drives, DVD players, VCRs, printers, scanners, digital cameras, and almost anything else you could imagine that passes information in and out.The system appears as a set of services that are available-some are software and others hardware, but the interfaces (user and programmatic) always present simply and uniformly the services available regardless of how they are implemented or where they are. In other words, the Jini infrastructure is a system architecture (hardware, software, and network) that supports the notion that a computing environment is a network-connected set of computing, storage, display, entertainment, communication, and IO devices. In a Jini system, devices can be added or subtracted, and doing so may alter some of the capabilities of the system, but it will not alter its identity or basic usability.
About Jxta: In other words, the Jini infrastructure is a system architecture (hardware, software, and network) that supports the notion that a computing environment is a network-connected set of computing, storage, display, entertainment, communication, and IO devices. In a Jini system, devices can be added or subtracted, and doing so may alter some of the capabilities of the system, but it will not alter its identity or basic usability.
About Jxta: JXTA technology is a set of open, generalized peer-to-peer protocols that allow any connected device on the network from cell phone to PDA from PC to server to communicate and collaborate in a peer to peer manner. JXTA has the technology that you need to write networked, interoperable, p2p applications that can easily: Find other peers on the network with dynamic discovery across firewalls Easily share files with anyone across the network Find up to the minute content at your favorite site Create a group of peers that can easily find each other, across firewalls, on any device Monitor peer activities remotely Securely communicate with other peers on the network As you can see, Jini focuses on how to provide a simple interface to the end uses while making the background service-providers transparent. Jxta focuses on how devices connected to the net can find each others and opearate together to make a difference.
" Veni, vidi, vici "<br />" I came, I saw, I conquered "
Hi Laudney, Thanks for your great info. It seems that Jini likes an Intranet (not over the public network) while Jxta can be deployed over the Internet. So, for instance, an instant messenger chat program (likes AIM or ICQ, not those web based IRC applets) between 2 PCs or among several PCs which connected to the Internet can base on Jxta P2P infrastructure to write the program. And, if I want to transfer file to a remote server which is connected to Internet, I can use Jxta as well without the need to use FTP? Thanks for your great help and I need to study more. Regards Andrew