The method I have proposed to fix this is "cycle trading". Traders submit their buy/sell requests for a trade cycle that happens every minute. Each cycle's trades go to completion if possible, based on buy/sell amounts and prices (bid/ask). Requests will be left over if they cannot be bought or sold in that cycle. They can be flagged to hang in there for the next cycle, or canceled, or changed.

But instead of a one minute cycle, let's do a one day cycle.

... Anonymous Coward. There are some very suspicious posts he makes. And besides, he seems to never sleep.

OK ... let's start a campaign to NOT buy USB. But we need something. Let's make our own replacement.

And I want to know your Slashdot nickname, too. I suspect YOU are concealing something. Oh wait.

If doctors get measured by success in this way, then they will be inclined to avoid the more risky patients.

I remember contacting that company about their system, and specifically asked about open source. I talked to some guy who was the sales manager for my area, and he seemed to get angry that I was asking for open source. I think that company was doomed by bad management.

Config-based does not mean sequential or non-sequential. It only means whatever is configured can be changed. What is needed to improve iptables and the like is optimizations like smart address lookup tables. This is actually doable in ways that have been around longer than patent periods but it is not iptables compatible.

This has nothing to do with running a server. It's all about bandwidth and nothing but bandwidth. They are giving you gigabit as a PEAK capability, not as a continuous rate. What they should do is specify the limits of their service in those terms like the maximum amount of data you can transfer in one second, one minute, one hour, one day, etc.

The reality is, most people will be downloading. That means most of the usage is in one direction. They will have plenty of capacity in the other direction.

One of the company executives actually came in to work one day.

So tell me what database software can run on multiple machines spread around the country, not lose any working data if any two locations go down at once (nor any resting data if 3/4 of the sites vaporize, so going to backups would not be needed for this), and handle 1000000 transactions per hour, and stay up 604800 seconds a week (continuously) despite plenty of backups. Once we have that, the rest will be easy, and can support older browsers and smaller PCs that poor people have ... HTML 3.2 FTW!

No one has their own country anymore. They can't even get all the white people out of South Africa.

... to not put any software or firmware on it at all. That way people just hire the kid down the street to load free software on it (or do it yourself).

Send them to me. Please include the power supply.

We cannot allow innovation to improve our connectors. Back to USB.

The stupid site won't even give real information until after you sign up. I don't want to give them sign-up info unless I decide to actually sign-up. But I cannot get the info to make that decision with.