|
|
Posted by Zeppelin on 12/29/05 14:03
> Won't work. Detecting the user's real ip only works if they are
> connecting directly to you or using a proxy which forwards the real IP
> address. Most proxies, especially corporate ones, are set up to not
> forward internal ip addresses. All you'll get is the proxy address -
> which may be shared by multiple users (as is the case in my company).
I know, and we will try do the best on this, but the effects of having
only proxy ips are not critical, our network will go slowly.
> So, instead of determining where the slowdown is, you're grasping at
> straws? Spending a lot of time trying to code something which could
> crash the server and may or may not resolve the problem, instead of
> determining the cause of the problem?
The needed code is trivial, trust me, only an array mantained through
client connections.
> I would think offloading some of the work would be more efficient. For
> instance, if you're supplying a download, have another server actually
> perform the download. Using a database? Put the database on a
> different server. And so on.
We are working on migrating other unrelated services to another
machines.
--------
I have now a beta version of the script using shared memory working,
thank you all for your time. I will be watching this thread, it could
be that anyone wanted know more about it, or if you liked discussing
more.
Thank you all ;)
Navigation:
[Reply to this message]
|