[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [syndication] RSS aggregators for non-technical folk

This is interesting. Some people like and some dislike (I am in this camp) using sharepoint for threaded discussions. For me, the drawback of sharepoint (for threaded discussions) is the lack of formatting and attachements and inline drawings. We do use exchange as a file store. Hm. It does work realy well for sending word documents around for editing. You can make changes and send it back very easily. If we had to use the file system it would be harder, and I would have to decide what to do with my copy. Now that you mention it, that is about as clever as storing web content in a database and serving it up dynamically (like everyone likes to do these days, at least until they get a mention on slashdot) when they could extract that content to a fixed page which is updated only when the data changes. To my knowledge, we haven't had any trouble with exchange reliability. We tend to notice when email goes down. 

Bill Kearney wrote:


Hi Doug,

Performance on an Exchange server is directly proportional to user behavior.

As in, if the users are dumb enough to keep attaching huge-ass powerpoint
documents to e-mail messages and cross-posting the bejesus out of them into
public folders then it will have an impact.  This as opposed to them being smart
and putting the file up on a fileshare and sending UNC shortcuts to it.  But
that would require effort and we know how well users take to THAT idea.

The single biggest mistake people make with Exchange is not following best
practices.  One should *NEVER* be using the Exchange server as a Domain
Controller and should /strongly/ avoid using it for filesharing.  That and it
really does benefit from (and use) more than one CPU.+1GB of RAM is a /very/
good idea.  CPU speed itself is not the limiting factor.

I've found it useful to have skulking programs that walk over the various
exchange public folders looking for stuff that's unusually large or has
attachments.  Messages are then sent to the admins, the author and eventually
(using ldap) to the user's management chain of command.  This usually gets them
back in line pretty handily.  Using robotic nag-o-matic code tends to effect
better behavior modification than letting people get caught in the possibly
political arguments.

The single biggest benefit to using an exchange server, and don't laugh, is it's
reliability and backup capabilities.  Compared to other stuff Exchange kicks ass
here.

-Bill Kearney

----- Original Message -----
From: "Doug Ransom" <doug.ransom@alumni.uvic.ca>



I saw the earlier versions of newsgator, but never tried it because I
have limited time and wasn't sure about the license
agreement.   I will try it.

From a usability and selling to execs point of view, outlook
integration is easy.  Convincing our IT manager (who's team supports
outlook) is another story.  If from within one client we could blog,
Wiki, aggregate, and have threaded discussions in outlook folders we
would be set (my opinion).  Our IT folk want to avoid any added burden
(threaded discussions etc) on the outlook/exchange server because they
say it will hurt too performance too much (instead we send word
documents to 100 people who each get their own copy in outlook instead
of one copy in a folder).
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/