|
|
Wednesday, February 20, 2002 |
|
Sam Ruby has nicely pointed several readers to this site, but the posts about my adventures with Radio/.NET/WSDL and the WSDL BDG are starting to roll off. Here is a quick list of links. I will roll these into a story a bit later... 3:52:42 PM [Macro error: The file "D:\Program Files\Radio UserLand\www\#prefs.txt" wasn't found.] |
|
2:59:02 PM [Macro error: The file "" wasn't found.] |
|
Who Owns The Content Managment System? This is one of those topics that has rankled me for some time. It is not that I think a CMS is wrong or even that the big expensive ones are evil. I do think they can be a waste of money, but that is another topic! I think IS needs to get out of content management. The content belongs to authors. 1:54:47 PM [Macro error: The file "" wasn't found.] |
|
Why is Radio 8.05 consuming an ever-growing amount of memory? If I leave it running overnight, 100M will be consumed by morning. It started at 16M this morning after I relaunched it, now it is up to 29M (three hours later). Six hours into the day and it hasn't changed much. Another hour; it has been hovering around 38M for a while. I guess I will leave it up tonight just to get a screen shot in the morning. ![]() 12:56:18 PM [Macro error: The file "" wasn't found.] |
|
Managing Stories in Radio Contrary to what you might see on this blog, I actually write a fair number of stories. Most of those, however, are targeted directly to the people I work. They are stories about topics that would not be of interest beyond our firewall or would be inappropriate to share with the public. For that reason I upstream all of my stories to an internal website. Once in a while, however, I will write a story I really do want to share on this site, my public site. I usually end up writing a post that is way too long to work around the fact that Radio's Stories support is geared towards a single website. or is it? I wonder how others are working around this issue? I can see a way to do create category-specific stories by simply creating a Stories subfolder within the category folder. Anything placed in there will get upstreamed to the category's destination. However, that approach loses the cool automatic index generation that you get from the normal Stories folder. Any other thoughts out there? |
|
[Sam Ruby's Radio Weblog] reports WebServices on WebSphere. WOW. 10:50:37 AM [Macro error: The file "" wasn't found.] |
