Hi!
I'm trying to send a small JPEG- image over TWSocket directly. If I send a
HTML coded page it works but not for an image.
This is what I send.
l.Add('HTTP/1.1 200 OK' + #13#10);// l is TStringList;
l.Add('Content-Type: image/jpeg' + #13#10);
l.Add('Content-Length: ' + IntToSt
Fastream Technologies wrote:
> Not yet. Having personal problems these days.. :((
I uploaded a new version with some common improvements
and fixes. There's a new option to hide the physical
path, see Menu | Options.
http://www.duodata.de/misc/delphi/OverbyteIcsFtpServ.zip
HomeDir is hardcoded C
Erik Brännlund wrote:
> Hi!
>
> I'm trying to send a small JPEG- image over TWSocket directly. If I
> send a HTML coded page it works but not for an image.
>
> This is what I send.
>
> l.Add('HTTP/1.1 200 OK' + #13#10);// l is TStringList;
> l.Add('Content-Type: image/jpeg' + #13#10)
On May 13, 2007, at 05:45, Erik Brännlund wrote:
> Hi!
>
> I'm trying to send a small JPEG- image over TWSocket directly. If I
> send a
> HTML coded page it works but not for an image.
>
> This is what I send.
>
> l.Add('HTTP/1.1 200 OK' + #13#10);// l is TStringList;
> l.Add('Conten
Fixed the problem I had with one server compiled with V5h
Bjornar added this line at several places :
if FKeepAlive = FALSE then {Bjornar} <-- added
CloseDelayed;
This particular server needs to answer other clients directly within the
OnGetDocument event of another client.
I
Hello,
I've tested one of my ideas for making SmtpCli working for me now.
I've constructed a thread which will do the sending of the mail and thus
does a thread attach/detach and has its own message loop.
It also knows the threadid of the main program so it posts a message to
it when the thread
Hello Markus,
Looks ok at first sight. But wy not create / destroy the component in
the thread's Execute ?
---
Rgds, Wilfried [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
http://www.mestdagh.biz
Sunday, May 13, 2007, 16:25, Markus Humm wrote:
> Hello,
> I've tested one of my idea
> {$IFNDEF NO_KEEPALIVE_CLOSE_CHECK}
>if FKeepAlive = FALSE then {Bjornar}
> {$ENDIF}
>CloseDelayed;
There are a lot of places where " if FKeepAlive = FALSE then {Bjornar}"
code is. Do have changed all ?
Why not act where FKeepAlive is assigned instead instead of where it is
> The thread also has a Cancel method which sends a special message to the
> thread which also makes it leave his message loop and does a abort on
> the control socket of the smtpcli and on the smtpcli.
Instead of wm_mailcancel, you can use standard WM_QUIT which makes
GetMessage return false so
Changed them all
> Why not act where FKeepAlive is assigned instead instead of where it is
> used
Wasn't sure that would work different in other places.
I can't test the service locally and the downtime of those servers have to
be an abolute minimum
Paul
- Original Message -
From: "Fra
Looking at all use of FKeepAlive, I think it is better to always set
FKeepAlive to false where it is assigned. This will add the header lines
accordingly in the answer. looks more consistent to me.
btw: Shouldn't you act on the client side in your application and set
keep-alive to 'close' (prop
Can check this next week maybe.
A proxy has it's own connection that can be keep-alive.
There should be no problem though, it's been tested with V3 even thru SSL
proxy's like the bluecoat proxy which does SSL filtering
Paul
- Original Message -
From: "Francois PIETTE" <[EMAIL PROTECTE
You need to handle exceptions, although this can be done in many
different ways the following (scribbled in OE) may show one possible
way:
procedure TThreadedMail.Execute;
var
msg:TMsg;
IsMessage : Boolean;
begin
try
mainform.SmtpCli.ThreadAttach;
try
mainf
Hi,
Sorry, I forgot to put a subject during the last post.
>> On a LAN even if there is no FTPServer active the
>> FTPClient takes 20 secs to timeout. I changed
Timeout
>> from 15 to 2 to no avail. I use
FTPClient1.OpenAsync.
> Try with FtpTst sample program.
> Try with Windows command line.
> > Try with FtpTst sample program.
> > Try with Windows command line.
> On one machine the results of
> Command line timeout = 20 secs
> FtpTst timeout = 20 secs.
As you can see, the timeout is the same for both ICS and Windows command
line utility. This means it is the default timeout impos
15 matches
Mail list logo
