![usa](/images/flags/usa.gif)
![us_minnesota](/images/region/us_minnesota.gif)
- Messages
- 1,925
rdwary is referring to "flaw" as a bug. Not as a design flaw. This is evident in his phrasing (plus he's called it a bug).
Many features have tradeoffs. Sometimes some people don't like one of the tradeoffs, and they insist it's a bug. It's not. It was deliberately designed to function in the way that it does. It meets the requirements set. The requirements were deliberately chosen.
It's not a bug (or a flaw) that my toaster can burn toast. Some users may think that's a flaw, but it's not. It's simply a tradeoff made in the design process. In order to give you more flexibility in the types of bread you use, and how much you want it toasted, it can end up burning the toast in some situations. This is deliberate, but the end result may not be what the user expects.
In this case, the vast majority of people would rather NOT have their computer go to sleep when they are streaming media from it. That would be absurd to let it go to sleep while it was obviously doing something you wanted it to do. Users would rightly call THAT a bug. Unfortunately, rdwary wants to do something different. Something it wasn't designed to do (go to sleep while media is streaming). That's not a bug.
There *MAY* be a bug involved here, but it would be in the client that is connected. If the connected client is keeping the stream open, even when it's not actually streaming, then that is a bug in the client, not the server.
Many features have tradeoffs. Sometimes some people don't like one of the tradeoffs, and they insist it's a bug. It's not. It was deliberately designed to function in the way that it does. It meets the requirements set. The requirements were deliberately chosen.
It's not a bug (or a flaw) that my toaster can burn toast. Some users may think that's a flaw, but it's not. It's simply a tradeoff made in the design process. In order to give you more flexibility in the types of bread you use, and how much you want it toasted, it can end up burning the toast in some situations. This is deliberate, but the end result may not be what the user expects.
In this case, the vast majority of people would rather NOT have their computer go to sleep when they are streaming media from it. That would be absurd to let it go to sleep while it was obviously doing something you wanted it to do. Users would rightly call THAT a bug. Unfortunately, rdwary wants to do something different. Something it wasn't designed to do (go to sleep while media is streaming). That's not a bug.
There *MAY* be a bug involved here, but it would be in the client that is connected. If the connected client is keeping the stream open, even when it's not actually streaming, then that is a bug in the client, not the server.
My Computer
System One
-
- OS
- Windows 8.1 Pro
- CPU
- Intel i7 3770K
- Motherboard
- Gigabyte Z77X-UD4 TH
- Memory
- 16GB DDR3 1600
- Graphics Card(s)
- nVidia GTX 650
- Sound Card
- Onboard Audio
- Monitor(s) Displays
- Auria 27" IPS + 2x Samsung 23"
- Screen Resolution
- 2560x1440 + 2x 2048x1152
- Hard Drives
- Corsair m4 256GB, 2 WD 2TB drives
- Case
- Antec SOLO II
- Keyboard
- Microsoft Natural Ergonomic Keyboard 4000
- Mouse
- Logitech MX