if you just slow down the connection you will have a lot of nearly idle apache processes running and so that after a while you cannot get more clients connected. Either just drop connections or use a single process proxy whith the required ability, which then forwards the requests to the apache. But restring by IP can be dangerous if users are sitting behind a proxy from the ISP (very common at least in Germany).
while I don't know if linux uses BSD code for crucial operation the author ignores that BSD uses GPL'ed code for crucial stuff: - compiler is gcc - debugger is gdb (this is at even true for the commercial BSD/OS)
we (a small german company) once outsourced some
stuff to romania. There was a strict task they
had to implement, but compared to what we do in-house the failed horribly:
- first problem was the language: they spoke a bad german and a bad english, so the best communication was between my boss and them, boss speaking a horrible english:)
- although we let them use their language of choice they did it in VisualC++, using DAO. They only cared about doing their job, not optimizing the code (like using indices for the database). Therefore the application got really big (due to the DAO installation) and slow (due to suboptimal database design)
- although the resulting code was good documented it is hard to change, because they did not think much about program maintanance (e.g. design it to be open for further development). No wonder, of course they hope, that if we need changes we need to hire them again
- they took twice the time they planned
On the other hand we used the same company for small work (stupid editing of word files, they could invent macros to speed up the work) and it went fine.
I guess it highly depends on what kind of job you have. For high skilled work I would rather use local programmers (so that I can see them face to face sometimes, that makes communication much easier) and if they are not available one could try a remote company. The most important thing I consider is a good communication, e.g. no language barriers.
If you are going for remote companies just to save money I would guess that you get what you deserve. Good quality isn't cheap.
in case anybody is interested... at http://noxxi.net/misc/mf.pl is a small script which simply renames all dangerous attachment names (which is everything except a view) so that they don't get executed on click. use it in the company I work for (mail gets loaded by fetchmail, piped thru this script and than forwarded to the recipient)
Slashdot Mirror
if you just slow down the connection you will have a lot of nearly idle apache processes running and so that after a while you cannot get more clients connected.
Either just drop connections or use a single process proxy whith the required ability, which then forwards the requests to the apache.
But restring by IP can be dangerous if users are sitting behind a proxy from the ISP (very common at least in Germany).
while I don't know if linux uses BSD code for crucial operation the author ignores that
BSD uses GPL'ed code for crucial stuff:
- compiler is gcc
- debugger is gdb
(this is at even true for the commercial BSD/OS)
we (a small german company) once outsourced some stuff to romania. There was a strict task they had to implement, but compared to what we do in-house the failed horribly: - first problem was the language: they spoke a bad german and a bad english, so the best communication was between my boss and them, boss speaking a horrible english :)
- although we let them use their language of choice they did it in VisualC++, using DAO. They only cared about doing their job, not optimizing the code (like using indices for the database). Therefore the application got really big (due to the DAO installation) and slow (due to suboptimal database design)
- although the resulting code was good documented it is hard to change, because they did not think much about program maintanance (e.g. design it to be open for further development). No wonder, of course they hope, that if we need changes we need to hire them again
- they took twice the time they planned
On the other hand we used the same company for small work (stupid editing of word files, they could invent macros to speed up the work) and it went fine.
I guess it highly depends on what kind of job you have. For high skilled work I would rather use local programmers (so that I can see them face to face sometimes, that makes communication much easier) and if they are not available one could try a remote company. The most important thing I consider is a good communication, e.g. no language barriers.
If you are going for remote companies just to save money I would guess that you get what you deserve. Good quality isn't cheap.
in case anybody is interested... at http://noxxi.net/misc/mf.pl is a small script which simply renames all dangerous attachment names (which is everything except a view) so that they don't get executed on click. use it in the company I work for (mail gets loaded by fetchmail, piped thru this script and than forwarded to the recipient)