usando k-logs e RSS para distribuir arquivos
barbaro. pra mim estao cada vez mais claras as
vantagens de k-logs. e pra Disney tambem.
leiam esse posting a respeito (eh de uma outra lista):
A defining aspect of a K-Log network is that it is an
extremely effective
one-to-many publishing system. What makes a K-Log
network effective (as opposed
to communications systems like e-mail, phone, and IM)
is its passivity. What do
I mean? People aren't forced to read what's published.
Readers only visit or
subscribe to a K-Log when they have a need to do so or
if they deem what the
author says is important. This passivity allows
readers to batch process their
reading and be selective about who they read. This
optimization saves time.
This feature makes K-Logs a great distribution system
for files (like
multimedia and office documents). Increasingly,
employees are using easy-to-use tools to create
audio and video files of meetings, events, interviews,
and more. They already
produce loads of documents that are often quite large.
So, how should people distribute this content? One way
is through e-mail
attachments. However, this method has two major
drawbacks. First, it bogs down
e-mail servers. Given that most people keep a
significant portion of their
e-mail on a server, an e-mail with a 2 Mb attachment
sent to 300 other employees
produces 600 Mb of bloat in the e-mail database.
That's not a good thing and it
drives sys-admins nuts given the limitations on e-mail
databases. Also, it
forces people to download it whether they are
interested in it or not. This is
particularly bad over a slow connection when on the
road.
A second way is to just post it to a file folder on a
file server. The problem
with this is that it strands the file, without
sufficient context. This context
is necessary. It provides people with a reason to
download the file.
Additionally, given the status of most files systems I
have ever seen, it will
likely be lost forever in a jumble of shared files. A
third way is to use
shared workspaces (collaboration tools).
Unfortunately, while these systems may
provide a small modicum of improvement in delivering
crucial contextual data,
they share the same limitations of communications
tools like e-mail: they work
best within the context of small groups and not very
well in a one-many
environment.
In my view, the best way to distribute a large file is
to publish it via a K-Log
to the Intranet. Here's why:
1) Sharing. Using this method people reading a K-Log
can find out how file
relates to the author's worklife; before they download
it. For example, "Here
is a video of a example sales presentation for product
xxx," or "I just revised
my marketing presentation for product yyy. It includes
some new graphs on
performance of the system that the product team thinks
are necessary to explain
to customers." This relevant information saves time,
effort, and limits
confusion. It makes effective sharing possible.
2) Trust: K-Logs introduce a large measure of trust
into the act of
distributing files. The file is attached to an
identifiable person within the
organization. Additionally, there is little threat of
virus laden files on a
K-Log relative to e-mail. The very nature of K-Logs
contains virus propagation.
3) Archives. With K-Logs, Intranet's become an archive
of what goes on within a
company. In regards to file storage, K-Logs provide
the archival data
necessary to understanding why the was created, when
it was created, why it
should be used, where it should be used, and much
more. Intranet search
functionality is also improved because the value of
the file is enhanced by the
number of K-Logs pointing to it (particularly when
Google's appliance is used).
4) Economics. Since only the people that want to
download the file download it.
Additionally, forwarding large files within a K-Log
context becomes a snap.
All I need to do to forward a file is to either post a
link to my K-Log for my
readers to use or send the link via e-mail directly to
people that could benefit
from it. Very simple and lightweight. There is very
little wasted bandwidth,
storage, or server utilization.
Another aspect of a K-Log network that is starting to
gain traction is distributing
files as part of an RSS subscription (Disney is using
this technique to distribute
large files to 2 m users). K-Logs automatically
publish syndicatable
content in the form of RSS (a standard syndication
format). That means if I am
using an RSS aggregator tool on my desktop, I can
subscribe to the K-Logs I find
interesting and get all the new posts automatically
without having to visit the
sites. Further, all of these subscriptions are
aggregated on a single "news"
page for easy scanning. Most people use this
functionality to keep track of an
order of magnitude more sites than they can through
simple bookmark-enabled
browsing.
What isn't well known is that it is possible to
include a large file as an
enclosure with an RSS feed. That means that
subscribers can automatically get
all files I publish, delivered to their desktop,
without having to go through
the process of active downloading. Enclosure
downloading can also be time
shifted to occur only during the wee hours of the
night to prevent congestion
problems (this can be done by simply typing in the
time you want things to be
downloaded). This also means that when a reader clicks
on a large file that has
been distributed as an enclosure, it launches
immediately. There isn't any
world-wide-wait.
There has also been some good work integrating P2P (a
clean corporate version of Napster
and KaZaA) into RSS enclosure distribution. This
would make distribution even
less expensive to do.
In conclusion, if you are a company that deals with
lots of multimedia files and
multiple revisions of documents, K-Logs should be a
simple solution to many of
your woes.
-----------------------------
barbaro, nao?
r'
=====
r
e
n
e rene@usina.com
+55 11 8193 1258
yahoo messenger: renedepaula
Bill Gates provides a simple explanation of weblogging and RSS
20/5/2004, 21:52
mais cross-posting:
Bill Gates provides an easy to understand explanation of the power of
weblogs and RSS (notification) that may be useful as a way to explain
it to your CEO...
_____________
"This (weblogs and RSS) is a very interesting thing, because whenever
you want to send e-mail you always have to sit there and think who do
I copy on this. There might be people who might be interested in it or
might feel like if it gets forwarded to them they'll wonder why I
didn't put their name on it. But, then again, I don't want to
interrupt them or make them think this is some deeply profound thing
that I'm saying, but they might want to know. And so, you have a tough
time deciding how broadly to send it out.
Then again, if you just put information on a Web site, then people
don't know to come visit that Web site, and it's very painful to keep
visiting somebody's Web site and it never changes. It's very typical
that a lot of the Web sites you go to that are personal in nature just
eventually go completely stale and you waste time looking at it.
And so, what blogging and these notifications are about is that you
make it very easy to write something that you can think of, like an
e-mail, but it goes up onto a Web site. And then people who care about
that get a little notification. And so, for example, if you care about
dozens of people whenever they write about a certain topic, you can
have that notification come into your Inbox and it will be in a
different folder and so only when you're interested in browsing about
that topic do you go in and follow those, and it doesn't interfere
with your normal Inbox.
And so if I do a trip report, say, and put that in a blog format, then
all the employees at Microsoft who really want to look at that and who
have keywords that connect to it or even people outside, they can find
the information.
And so, getting away from the drawbacks of e-mail -- that it's too
imposing -- and yet the drawbacks of the Web site -- that you don't
know if there's something new and interesting there -- this is about
solving that.
The ultimate idea is that you should get the information you want when
you want it, and we're progressively getting better and better at that
by watching your behavior, ranking things in different ways."
XP vai ficar mais seguro?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
17/5/2004, 06:51
materia na anchordesk sobre o proximo "remendo" do XP. interessante
eh que, para aumentar seguranca, algumas coisas de "internet" vao ser
bloqueadas por default:
> And while MSN has had pop-up blocking in place for some time, SP2
> will take things a step further. Adware and spyware writers'
> favorite tricks will be banned by the pack: Microsoft have promised
> no more pop-unders, no more unwanted Flash ads, no ads bigger than
> the screen so that you can't find the close box, that kind of
> thing.
http://zdnet.com.com/2100-1104_2-5212568.html?tag=adnews
abracos
r
e
n
e'
rene@usina.com
http://www.usina.com
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.1 (Build 307) Beta
iQA/AwUBQKiLZlO1BMLbAt3oEQLBCACg4+DKPHjKMYsEiJYBPW1/2zc7qv4An19r
0qm2R0Nzr12cyao9sTS4FUEy
=fKhM
-----END PGP SIGNATURE-----
straight forward
