Re: [ANet-devel] Thoughts on optimization

[Benoit N. <be...@ma...>]

>Okay, let's look at what we're up against as far as network optimization.
>Some real quick thoughts here about what we have to avoid...
>
>Searches -
>Overly expansive searches without a mechanism to handle them. Ex. *.mp3
>Searches that take to long to play out. Ex. Searching for to many hops,
>would create extra of pressure on the nodes that are in direct contact
>with the reciever.

My example of "Passive File System" is much better, I think, because it's
much like FTP: there is NO searching systems at all. You just wait for file
lists, distributed as static data, and once those file lists are on your
computer, you search them on your computer, not on the network. And I
personally prefer file browsing than file leeching... (See last chapter in
Part 1 of the docs)

No one should be allowed to create a query with too many hops, as this will
be considered as spamming and your node will be disconnected from the
network. There is already a mechanism to "plant" a query in the middle of
the network with gateways (Part 3 in the docs, actually a previous posting
in this mailing list).

>Services -
>Bandwidth hungry services. Ex. Streaming content that is not properly shared.

That's a though one. I don't think streaming content (more than just text)
would work properly with the current way ANet is defined...

>Abusive use of services. Ex. File Leeching from a single source.

Again partly resolved with passive file browsing.

>Inappropiate service. Ex. Running too much on too little.

I think that could be considered as a form of spamming (even if it isn't,
like a big, fat 100KB/sec streming video), as it is abusing of the
bandwidth of the network. No?

- Benad