After a week of vacation I’m back again. I’ll summarize the wave news that I have found for the week.
- Process-One claims on my post that they have made a wave implementation in their software. I cannot find anything about this implementation on their website, but it looks like they are a company which works on Jabber XMPP. So they already have the experience in the protocol framework. Going to be interesting to see a demo of the solution.
- It is now possible to sign up to Google Wave for my domain. Just go to the form and fill out the detail. They don’t say anything about when Wave for my domain will be open for demo. For enterprises it will be a must to have a wave account for their domain. If they had to use regular accounts on the standard Google application it would be very difficult to manage access controls and users.
- The first Danish Google Wave hackathon was performed by Tommy Pedersen. Blog about the event in Danish or translated to English.
- GoogleWaveBlogger has create the article 5 Things Wrong with Google Wave. It gives detailed descriptions the problems with Google Wave. It mentions security, spam, replacement of Google hosted Apps, integration with MS office and Enterprise server installation.
I have probably missed something, so please let me know with a comment.
It is really fun to be a part of how much Google Wave is being hyped and talked about. I’ll try to write about some resources that I found in the last week or so. If you have other post that I should post please send them using firstname.lastname@example.org, and will try to put them in the next news.
- I have written a blog at SAP developer network, with information about how SAP can Google wave can collaborate. There is a demo of calling enterprise services (ES) from Wave robots.
Tommy Pedersen shared the link to what is coming in the API.
It looks like the developer preview will stop on September 30th, and then we must hope we can get an account on the production system. So we will not float without wave access for a long time.
What is interesting is that Douwe Osinga from Google is sharing, what they believe they can achieve before the end of the developer preview.
The things I think is the most exciting news are the following:
- The Robots can use other addresses that email@example.com. That could mean you could have more robots on the same application making the robots tailored to the user. Also we will see that robots will exist on our own servers and not app-engine.
- A better integration between robots in to Wave, so they robot can perform tasks even the wave is not active by a user.
- OpenSocial integration for both robots and gadgets. That is something that I’ll need to look more into.
- Insert simple HTML into the waves. This is not possible now, so the robots can make some better looking content easy. Then we need to consider using CSS on the document.
- Open source the robot API it does not matter much now, but for the adoption that will probably make things easier.
I’m impressed with the plan Google has created for the development of the Google Wave API. I hope they have made some of the improvements already otherwise they will have a hard time implementing them all.