Interesting.. the site update isn’t updating anyone yet for CF1 and they did some goofy naming in the updates
Tags :Sametime
I already had the site specified for all the users in stconfig.nsf. It was the same one I used before for the patches for the Sametime Gateway in 7.5 CF1 world. Unfortunately it is not updating the clients now with the changes. I am doing this in stages, meaning I have not rebooted the Sametime server since changing the site.xml file. It shouldn't need to be done, so I didn't. I simply updated the xml and waited for today. Nada, nothing.
So looking at the local files in the plug-in directory you already have for Sametime Connect 7.5.1 compared to the new site update, none of them seem to match from the first 10 iI checked. Either they had
com.ibm.collaboration.realtime.feature.version
listed instead of the new ones that did
com.ibm.collaboration.realtime.751.CF1.feature
or they were entire new features that did not exit before. So the new ones should come right down. But how about the ones that do the same thing but compete? Shouldn't they simple update the date at the end of the feature line. Instead of
com.ibm.collaboration.realtime.sprite_7.5.1.20070416
They go and toss some oddity name of
com.ibm.collaboration.realtime.sprite.feature._7.5.1.20070723-1402
How does that update the existing one or how does it know which to use unless called from somewhere else? How can we clean up these older ones with the updates?
blog comments powered by Disqus
On Friday, August 3rd, 2007 by Chris Miller
