Hello:
I have updated the Wiki to include an explanation of the LineEdit
property. I must admit that I didn't really pay attention to what it
did, and thought it was only transliterating backspaces. Since I was
testing my server by telnetting from a terminal, this seemed like a
good i
I have already told you the best way. Make the listening IP 127.0.0.1 .
On 12/4/07, George <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I created a THttpServer that is used as a middleware between my delphi app
> and a flash application.
> I want to make sure that only me and flash will communicate e
Hello,
I created a THttpServer that is used as a middleware between my delphi app
and a flash application.
I want to make sure that only me and flash will communicate each other so I
want to restrict connections
from outside internet or local IPs. What's the safest way to check it? Any
piece of
George...
Fundamentally, there are really only two ways to constrain inbound
connections regarding client identification. As I am sure you are aware,
keep in mind that neither TCP nor HTTP have any built in mechanisms for
facilitating client identification or rejecting connections based on any
ru
George,
I think Hoby's response is excellent, but I wanted to
add a few suggestions based on my interpretation of
your problem.
1. If the source address of each of the hosts that
will communicate is known, then you can check for
this using the GetPeerAddr method from within the
SessionAvailable m
Great additional info, dz. Thanks... Hoby :)
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of [EMAIL PROTECTED]
Sent: Tuesday, December 04, 2007 10:25 AM
To: twsocket@elists.org
Subject: Re: [twsocket] Webserver only with local connections
George,
I th
Hoby Smith wrote:
[Big snip]
> For example, you could use, TMyHttpConnection(Client).GetPeerAddr, to
> get the client's address and then determine if you want to disconnect
> it. You would have to provide this logic and any rules as you need.
There are helper functions available in OverbyteIcsWi
Hi Arno,
Thanks for the insight. More questions below:
Arno Garrels wrote:
> Jake Traynham wrote:
>
>>So, it seems that for every time ASyncReceive looped, there would
>> still be a message (FD_Read??) being put in the queue to call it
>> again, which would call my DataAvailable event ag
Hello Jake,
> However, I would like this code to work/receive as fast as possible. The
> comment in the code where wsoNoReceiveLoop was introduced says that this
> option gives "lower resource usage with really fast LAN and large
> transfers". Does that mean it's faster, or just uses less memory
> No never do that. Don't set wsoReceiveLoop. If something is still (or
> again) in receiving winsock buffer when you leave OnDataAvailable then
> it will trigger again in a loop.
I don't agree with this.
I had troubles with a httpserver crashing when large files were transmitted
on a high speed
10 matches
Mail list logo
