search for: implemeneted

Mocha''s mock/stub framework has the ability to stub all methods on a mock given. Does RSpec''s mocking framework have this ability? And if not, is there some reason it shouldn''t be implemeneted? Regards, Scott

I have three Icecast-2.0.0 servers up with possibly more coming online. I am trying to figure out how to do more intelligent load balancing between the three. Problem: There are bandwidth restrictions at a couple of the locations. Current Solution: Round-robin DNS (with very low TTL) and a restriction on the number of listeners on the servers where bandwidth is an issue. I am finding this

> I am finding this solution to be sub-par. Client-side caching seems to be > one of the culprits. When one of the bandwidth-constrained server IPs is > selected, and it's full, it seems that the client never switches to > another server on reconnect. Using Winamp as the client right now on > Windows XP (for testing). Only flushing all the DNS caches up the chain >

How does this affect the fallback-mount(s) if the main mount isn't being used? <p>>Th redirect should of course include some info in the redirect URL >regarding how many times it's been redirected - you don't want to get >into a situation where users are bounced around indefinately. > >Personally, I'd go a step further and collect performance data so that

On Wed, 5 May 2004, Jack Moffitt wrote: > If the client limits are hit on the server, it sends back an HTTP > redirect with the location of a random mirror (not itself). This should > be transparent to clients and acheive the affect you want. You could > also combine with with round robin DNS to spread people over the servers > initially. > > Seems fairly elegant.

...that it > works on Debian stable and other other releases with compilers, libraries, > ... that may be a few months and releases old. You didn't say which > Kubuntu you are running The latest, Dapper Drake (6.06). > -- but you may not have to follow Christian's way > as implemeneted in the stable port (and hence his way of dealing with > r-recommended as a big 'sumo' package). You could just install the CRAN > packages directly, or build from my Debian unstable sources (instead of > rebuilding on CRAN) -- a more 'offensive' approach. > > Anyway,...