|
Monday, October 07, 2002 |
|
A dozen or so of us have been tossing around a lot of great ideas in the Groove Experiments shared space. One of our concerns, of course, is how to seemlessly share our findings publically with a wide public mechanism. Tonight, we decided to re-focus completly in a new direction, one direction. We felt that instead of continuing to be somewhat abstract that it would be better to take one of our ideas, discuss it, form requirements, and start writing code! We have decided to focus on a Groove to Weblog interface. We do realize that there have been two previous partial implementations that we will be looking at: Tim Knipp's Blogger Tool and the Agora Groovelog. One of the members is looking into those two. We realize that this kind of dump from me here now is not optimal. Ideally we would like to have things available in real-time as they happen publically. Maybe this Tool or Solution will go a long way toward that. 11:37:58 PM 
|
|
Five of us are at this moment, working from five different places in the world in Groove Experiments doing the Requirements and Design of a Groove to Blog tool. Real time. Amazing. Talk about Extreme Programming! 9:58:24 PM
|
|
Groove Network status. SB Chatterjee : During the past few days, the Groove networks were slow - there is a barrage of end-user gripes in the Groove Forums. I am finally "synced" up - took awhile, over 48 hours ! I think *one* good way of dealing with this is by having a Groove Infrastructure status page that shows the health of the infrastructure. [Jeroen Bekkers' Groove Weblog] 11:56:29 AM
|
|
Winfessor, a development firm for Windows collaboration tools, and Tipic, provider of Windows based Jabber servers, announce the availability of a native .NET SDK. Winfessor’s SDK supports both enterprise and mobile messaging while Tipic’s server provides secure corporate messaging for the enterprise. The combined tools allow developers to create collaborative applications that can be integrated with instant messaging from Yahoo! Messenger, AOL Instant Messenger, MSN Messenger, and ICQ 8:30:02 AM
|
|
Web Services Threat Detection. Justin has a response on this: "Greg is asking about something that is near to my heart - Web Services Threat Detection. Unfortunately the best answer I ever came up with is this - I couldn't do it in 100% code. It requires people. I could monitor everything that comes in (who, what, when, and from where). I could check whether or not they were supposed to be sending the particular type of message at that particular moment in time. So what did I end up with? Nothing tangible. Just a bunch of ideas. Maybe I'll get a chance to implement them at the next gig... " BTW, this is one of the topics we are taking up in our Groove Experiments space. 7:48:57 AM
|
|
Server-Side Asynchronous Web Methods. From Sam - Server-Side Asynchronous Web Methods. Justin has some great follow-up: " That is a very good article. It explains something that I've never seen mentioned in the documentation[1][2]. ... This is an awesome paradigm. I always questioned why you would want to expose your database as a web service. And here you have it. I wish I had some perf numbers for you, but I don't. And I wish I could tell you that I've done with this MS SQL Server, but I haven't. I have done it with Oracle 9i using XSQL (proprietary technology) through Tomcat 4.0.x. It works GREAT. I loved it. The main problem I had with XSQL is that there is no native proxy generation code. I had to use HttpWebRequest and friends. Not terribly complicated, but not nearly as nice as the proxies that WSDL.exe generates for you. Now if you are only accessing one table with one query, making it asynchronous isn't going to gain you anything. In fact, it might hurt performance because of thread context switches. But if you have multiple queries to run and you can wait on the results, it is a really cool way to do it. " [1] - if anyone knows where in MSDN this is documented, I'd really like to see it. Let me know. 7:48:37 AM
|
Last update: 11/1/2002; 8:24:30 AM .
