| | LotusLive
Tuesday, 10 February 2009 21:42:28 EET | | |
| | Today I registered and tried out LotusLive: apps.lotuslive.com.
LotusLive is a web browser based global conference tool, which works very similar to a SameTime conference.
The benefit over SameTime is that you don't have to install any software (only browser plugins, and a bunch of SSL certificates), and that the meeting is available on the internet, globally.
The people who are invited to a meeting (anyone can be invited who has internet access) can use Firefox or IE, but the host needs both browsers to create a meeting.
The meeting must be created with IE8 (since sharing apps doesn't work in Firefox, it just hangs), and then the invitation must be sent with Firefox using a different LotusLive account, since the sending of an invitation doesn't work in IE8.
Alternatively, Firefox can be skipped, if the invitation is sent via normal mail (there's a link for that on the main page of the meeting hosting).
You can also use SMS or instant messaging to send the link directly to your invitees using a URL pattern like this: https://apps.lotuslive.com/meetings/join?id=123-456, where the 123-456 is the meeting ID.
I tested to share single application, and also to give control to a colleague, and it worked fine.
It was a bit slow, using Notepad++ as shared application, or a OpenGL 3D engine application, but it worked.
LotusLive meetings have also a live video stream, which I didn't try yet, but I think they could be used to give better realtime application performance, and also live audio and video.
If the bandwidth could be improved, it could really replace coorporate SameTime conferences, and adding the feature that also external vendors and customers can be invited to the meeting. This could potentially eliminate a lot of travelling costs around the whole world.
I read in the news that Obama is putting 825 billion dollar to raise the bandwidth in USA, so this will be positive for LotusLive also, as well as for creating 2.5 million new jobs and getting the broadband to schoolkids and hospitals.
| | |
| | |
|
|
| | Domino 7.0.3 is still the most stable release
Monday, 02 February 2009 18:34:13 EET | | |
| |
After a year of testing Domino 8, it still has bugs which prevent it from being used in production.
- Agent Manager crashes Domino
- HTTP agents which open a view and user closes the web page before the agent finishes, causes the agent never to end
- I suspect this agent orphanization happens also under other circumstances, but it does never happen in 7.0.3
- Domino 8.0.1 on openSUSE 11.0 has been very stable though, so I suspect that it is mostly Windows Domino 8 related
The recently released 8.0.2FP1 caused a server to shutdown unexpectedly today.
- I'm still monitoring this behavior, and if it repeats, I need to upgrade to 8.5
- Now it shutdown the server 2 times, and I upgraded to 8.5
- It has been stable after upgrading to 8.5
Domino 8.5 has crashed several times on our AIX server, and only once it has even left a nsd file to diagnose.
- However, on other servers (Windows 2003 32-bit), it has worked fine so far
- Also all other Domino versions crashed on the AIX server
- Quite often even AIX itself crashes, and needs an IPL to recover
- I got AIX 6.1 CDs now, so I will try if upgrading the AIX5L 5.3 version will cause less often crashes
- Domino 8.5 has also a bug which causes the compact command to increase the file size, instead of reducing it
- It could be that Domino 8.5 is unable to use design and document compression, this would explain the size increase, which can be fixed again by downgrading to Domino 8.0.2 and compacting there
Domino 7.0.3FP1 has crashed exactly at the same time every night.
- This is a known issue due that Domino+Tivoli+TSM+Remote Desktop doesn't work together, and the workaround is to run Remote Desktop with the /console option
- I'm monitoring now if this workaround causes less crashes, if not, then I will need to downgrade to 7.0.3
- This workaround, suggested by Alise Latvia, seems to have fixed the problem
Domino 7.0.3 crashes sometimes, but it leaves a nsd behind, so the causes for the crashes have been fixed or workarounded.
- Most crashes were caused by other causes, like FTI corruption, harddisk failures, etc... Only a few cases remain where the cause of the crash was left unknown.
- Monthy average uptime of 99.5% is easily possible with Domino 7.0.3
| | |
| | |
|
|