|
|
Posted by Jerry Stuckle on 08/24/07 11:24
Piotr Nowak wrote:
> Jerry Stuckle pisze:
>> Erwin Moller wrote:
>>> Jerry Stuckle wrote:
>>>
>>>>
>>>> HTTP just isn't set up for this sort of thing.
>>>>
>>>
>>> True, but it can be misused for it.
>>> Long ago I made a site do just that (before Ajax/xmlhttprequests) via
>>> hidden frame refresh.
>>> It sucked of course. ;-)
>>>
>>
>> And how often have we seen things misused by incompetent
>> "programmers"? :-)
>>
>>> Java <--> JavaScript is a much cleaner solution.
>>> But if memory serves me well the visitor had to give the applet
>>> rights to listen to another port than 80.
>>> I am kind of rusty with Java these days, so things might have changed.
>>>
>>> Regards,
>>> Erwin Moller
>>
>> It depends on your security setup - but if you do need to give it
>> rights, it's easy enough to do so.
>>
>> Of course, there is another downside to this - maintaining what could
>> be thousands of connections at the server. That has its own overhead.
>>
>
> Two drawbacks:
>
> - firewall on client machines
> - too many connections
>
> thanks for advice anyway :)
The firewall would have to be adjusted, of course.
And while I normally don't recommend maintaining open connections like
this, the overhead of opening and closing thousands of connections every
10 seconds would be much higher on both the server and the network.
Establishing connections is an expensive process, both in cpu cycles and
network. Maintaining open connections takes very little of the network
resources, a little server memory and a few CPU cycles.
Yes, you're wasting server resources by keeping rarely used connections
open, but you're wasting even more by constantly opening and closing them.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================
Navigation:
[Reply to this message]
|