Archive for March 2004


Build 119

Build 119 is out. The big news here is presence support. There is a Buddy List that will allow you to see who is online and who has been online. Chat works just as before.

Changes for 0.1.119 (30 Mar 2004):

  + File sharing and buddy list Panels added to main GUI
  - View Switcher updated to accommodate new panels
  + Group List now Alphabetically Sorted by Kernel
  + Custom Renderer for Buddy List added
  + Join/Leave buttons now work for the Buddy List
  - Improvements made to the RDV monitor (tracks time for connection, more consistent output)
  - Changed RDV search timeout to be 2 minutes (hopefully your wait is allot shorter than that!)
  + Basic presence service created (needs work, not exactly efficient, good enough for now)
  + Buddies (peers) now display in status view
  + Custom Icons for Buddies
  + Buddies for a group updated by heartbeat thread (once every 10 seconds)
  - shutting down the application now triggers client to leave all joined groups
  + Peer name now shows in title bar once connected to JXTA

Mindshare RDV0 � New Permanent RDV For The Mindshare Group

When your client is searching for and RDV in the mindshare group you should see a message like this in the log:

rdv monitor:INFO: Group 'mindshare', Waiting for rendezvous connection...

I have set up a permanent server running mindshare at this ip address: ’′. It should be reachable if you have configured your client correctly. You should see the following line in the log if this server is successfully found:

rdv monitor:INFO: Group 'mindshare', RDV Event 'RDV CONNECT', peer 'Mindshare RDV0'

If you see this instead:

rdv monitor:INFO: Group 'mindshare', RDV Event 'BECAME RDV', peer 'Your Peer Name'

It means that your peer could not find my server and became an RDV itself (as it is designed to do). It also means that it is unlikely that you will become connected to anyone else. Please check your network config and environment if you have this problem. Delete the �.jxta� directory in the folder where you installed mindshare to run the Configurator again.

Nightly Build 0.0.112

This build adds a bunch of diagnostic stuff and gets rid of the annoying password dialog. You�ll need to delete your ‘.jxta’ directory when you install this release. Also the distribution now unpacks into a ‘mindshare’ folder to save you the trouble of creating one. Get it here.

I also have a hunch that using the ‘Use Only Configured Rendezvouses’ in the ‘Rendezcous/Relay’ section of the Configurator might help with some of the connectivity issues we are seeing.

Change Log:
+ RDV monitor now reports what type of event occurred and what peer was involved, by peer name if possible
+ RDV monitor now runs continuously for the life of the group
+ RDV monitor code pushed down into PeerGroupManager
+ Save button for the log window now saves the log file when pressed. File names are generated automatically.
+ Distribution package now extract to a folder ‘mindshare’ with all resources inside. Just use “Extract here” in winzip etc.
+ Pesky password dialog is not suppressed.
* The StreamCorruptedException is now caught and ignored.

First Group Chat Test

The first group chat test build is available from the nightly build section. Here are the instructions for testers:

  • What You Need To Run Mindshare
  • A computer running Suns Java 1.4.2. Any OS will do and you are certainly welcome to test on Linux and MacOS X.
  • No firewalls actively blocking connections to that computer.
  • If you are behind NAT (you have a cable/DSL router with more than 1 computer attached) you need to enable port forwarding of ports 9700 and 9701 to you test computer. Alternately you must use the HTTP transport (see details later).
  • the current build
  • the invitation file to the Chat Test Group
  • Where To Get The Build and Invitation file:

  • How To Install It:
  • Just unzip it where you want the application to live. It unpacks itself into a folder called ‘Mindshare’.

  • How To Run Mindshare
  • If you are on a modern OS and suns Java is properly installed: Just double click on the ‘mindshare.jar’ file to launch the program If you OS is challenged go to the command line, switch to the directory where mindshare.jar is located and type:

    >java -jar mindshare.jar

    Once its running go click ‘Connect’ on the toolbar. A big dialog will appear called The ‘JXTA Configurator’. This is the network library and it wants to know a bit more about your computer. You will only have to fill this out once.

  • How To Use The JXTA Configurator
  • This all depends on your network setup, firewalls and NAT at your location. Read this (im serious) to figure out whats what: Using the JXTA Configurator
    Ideally you want to be using TCP/IP transport and have either a straight connection to the Internet or have a port forwarded to your computer for JXTA. If you are using NAT you will need to go into your NAT software or router and determine you external Internet IP address. If you are using TCP/IP turn off the HTTP transport, you wont need it. Never have your peer act as a Rendezvous peer, mindshare will take care of that.

  • How to Get Connected To The Chat Test Group
  • Once JXTA is configured it will take up to 2 minutes for the client to connect to the network. Be patient. You’ll probably see the log stuck at: “rdv monitor:INFO: Waiting for rendezvous connection…” for quite a while. Its just trying to find other computers on the network. When the client is connected the ‘Accept Invitation’ option in the File menu will become available. So go File->Accept Invitation and point to the invitation file you downloaded. Once thats done select the group from the drop down list on the main toolbar. Click the ‘Join’ button on the toolbar. Once again, it may take a while to connect to this group. You can watch the log and to see whats happening. When the ‘Leave’ button becomes enabled you have joined the group.

  • How To Do Some Testing
  • Click the Chat button on the toolbar to show the chat window. whatever you say will be sent to the entire group.

  • report bugs!
  • If it doesn’t work, if it explodes, if it melts you computer, let me know about it. send e-mail to: