Submitted by James Purser on Mon, 18/01/2010 - 08:23
Well it's the end of day one of linux.conf.au here in Wellington and I have to say it's been a pretty good start to the event.
Breakfast, or so it claimed:
I left sleepy Dapto at 4am yesterday morning to make it up to Sydney for my 8:45 flight. Everything went well, and I met up with other lca attendees (Melissa Draper, Michael and Brett Morgan). Check in was fine and we were soon boarding. I took out my copy of LotR and the trip commenced.
Submitted by James Purser on Sun, 25/10/2009 - 05:39
Okay I've added a new section to the FedOne book. This time we're concentrating on the FedOne Agent framework, which provides the same sort of functionality to FedOne that the Robots API does for Googles own Wave servers.
FedOne Agent Framework
Submitted by James Purser on Wed, 07/10/2009 - 13:23
I haven't blogged for a little while, and my only excuse is that I've been concentrating on doing rather than writing about it.
Anyway I thought I would put down some notes about the stuff I've been doing with Google's Wave and the avalanch that has been the launch of the new Beta Preview.
Submitted by James Purser on Fri, 21/08/2009 - 01:17
If you're running the Wave Reference Server I would suggest that now is the time to update and rebuild it. In the latest release of the code, the guys at Google have added "Agent" support and an echoeyagent to demonstrate how to write your own Agents.
Agents fulfil the same roles as Robots in the Wavesandbox, being programmatic participants in the wave which respond to other users.
So let's see who can write the first third party agent.
Submitted by James Purser on Wed, 12/08/2009 - 03:06
I'm a parent to three wonderful and sometimes wonderfully frustrating children. Each of them has gone through that stage where they see something they like and believe they need to cram as much as they can in their mouth at once. You parents out there know this bit, their eyes bug out as they realise that they can't move their jaws because they're crammed to overflowing. What usually results is a huge mess and tears.
Submitted by James Purser on Sun, 09/08/2009 - 04:40
Okay so now that you've got the WRS all setup and federated, you're talking to people around the world with the console client and wondering what to do next.
Well personally I think the next thing to do is have a look at what needs to be added to the WRS to move it beyond "Reference" and into something that can be used to really explore the Wave Concept.
Below is what I think the WRS is going to need and why:
Client:
The WRS needs a web based client for a couple of reasons.
Submitted by James Purser on Tue, 04/08/2009 - 02:19
Submitted by James Purser on Sat, 01/08/2009 - 01:49
Okay I've got version 0.1 of a WRS installer script here.
It's a bash script and has been pretty well tested in Ubuntu. It does have an alternative for Redhat based distro's but this is basically untested. The script itself is meant to manage the downloading and installing of the various pieces of software required to setup the server. It doesn't handle the Openfire management or DNS setup you will require.
Submitted by James Purser on Sat, 25/07/2009 - 22:55
Submitted by James Purser on Fri, 24/07/2009 - 09:48
*** Edit the information contained here is out of date. To find more up to date information please visit here: http://wavingtheshiny.collaborynth.com.au/books/fedone-book/fedone-book ***
When Google announced the new Wave technology at the IO conference earlier this year they made a promise. That not only would the Protocols be Open, but they would also be Open Sourcing "the Lions Share" of the code they were developing for the Wave.
Pages
