Thank you guys for your quick replies.
I reply here to your different messages.
Kirk Dunlap wrote:
> Geppy,
> It would be helpful to see how you are receiving it. Show us some code on
> the receive side of this.
as server I used the one contained in Wilfried's example server1.zip at
http://t
Hello,
This is not directly a ICS question or issue however someone here might
have experience and may guide me.
Has anyone ever developed a Z39.50 client?
A client that can search for a book in a public library's database.
If so, please contact me directly.
Regards
Perry Jönsson
--
To unsu
Ever wanted to know who are the ICS experts taking time to answer your
questions ?
Just have a look at this page:
http://www.overbyte.be/eng/overbyte/teamics.html
Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html
--
[EMAIL PROTECTED]
The author for the freeware multi-tier m
> It is my understanding that THttpCli does not timeout.
> Say, it has connected to the web server and sent the request.
> But if the server doesn't send anything back, THttpCli will
> not timeout. Am I correct?
TCP/IP has timeouts for opening a connection, although not usually once
the connectio
Hello Jack,
> I wonder why would winsock even time out in this case?
> Isn't it legitimate to have a socket connected and doing nothing?
Yes of course. As always I anser to fast without carefully reading the
request :( If yoiu connect and do nothing noone will timeout of course,
unless the server
> Starting from various TCP client inlcuded in ICS examples, I tried to
> send through TWSocket a mix of text commands and records but I wasn't
> successful.
>
> On the server, I receive correctly the text command but not the
> record. What I'm doing wrong?
You would need to be listening with
Hello Wilfried,
I wonder why would winsock even time out in this case?
Isn't it legitimate to have a socket connected and doing nothing?
--
Best regards,
Jack
Wednesday, October 26, 2005, 1:35:36 PM, you wrote:
> Hello Jack,
> real quick answer :)
> correct !
> Winsock will timeout after a
Thank you Wilfried and Arno for the real quick replies :)
> Winsock will timeout after a while, but this is depending on many
> factors and can take a long time. For automated aplications use your own
> timeout.
Any idea how long it can be? Like, a few minutes? or hours?
>> Real quick question.
Hello Jack,
real quick answer :)
correct !
Winsock will timeout after a while, but this is depending on many
factors and can take a long time. For automated aplications use your own
timeout.
---
Rgds, Wilfried [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
http://www.mestdagh.biz
W
Hello Geppy,
As Kirk and Arno mentioned show us how you receive the data. maybe one
remark at the moment:
>wsocket.LineMode := True;
>WSocket.SendStr(EditCommand.Text + #13#10); // the command is 'DATA '
>// r fields filled with some data
>pr := @r;
>wsocket.LineMode := False;
Jack wrote:
> Hello,
>
> Real quick question.
>
> It is my understanding that THttpCli does not timeout.
> Say, it has connected to the web server and sent the request.
> But if the server doesn't send anything back, THttpCli will
> not timeout. Am I correct?
Yes, unless Winsock times out.
>
>
Geppy Piloni wrote:
> On the server, I receive correctly the text command but not the record.
> What I'm doing wrong?
Is LineMode enabled on the server-side?
What does your DataAvailable handler on the server?
Arno Garrels
--
To unsubscribe or change your settings for TWSocket mailing list
ple
Hello,
Real quick question.
It is my understanding that THttpCli does not timeout.
Say, it has connected to the web server and sent the request.
But if the server doesn't send anything back, THttpCli will
not timeout. Am I correct?
--
Best regards,
Jack
--
To unsubscribe or change your settin
Geppy,
It would be helpful to see how you are receiving it. Show us some code on
the receive side of this.
Kirk
On 10/26/05, Geppy Piloni <[EMAIL PROTECTED]> wrote:
>
>
>
> Hi all,
> I'm trying to implement the client server architecture described here:
> http://tinyurl.com/benop
> My first app
Hi all,
I'm trying to implement the client server architecture described here:
http://tinyurl.com/benop
My first approach was with Indy 10, but after some attempts, I found quite
difficult to manage the complexity of multithread programming, so I dropped
Indy and now I'm trying ICS.
I had a po
Hello Ian,
Yes I have faced this problem before. Not exactly remembering how did I
passed it but creating a fresh package would help (IMO).
Best Regards,
SubZ
- Original Message -
From: "Ian Tuck" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, October 26, 2005 6:16 PM
Subject: [twsocket] C
Bjørnar Nielsen wrote:
>
>
>>That's an old bug in OE, you should not copy M$ bugs but wrap
>>the subject line. BTW: I think having ~1000 chars for the
>>subject line is far enough, or do you know a client that
>>would display such long subjects properly?
>
>
> I just testet Outlook, and it
Hi. I've seen this question asked before, but didn't see a solution posted
in the archives.
I've just compiled the latest beta of ICS, and when I attempt to install the
packages, I get a warning that BCB can not install the package because
bcbie60 already contains the unit shdocvw_ocx. Has anyone
> That's an old bug in OE, you should not copy M$ bugs but wrap
> the subject line. BTW: I think having ~1000 chars for the
> subject line is far enough, or do you know a client that
> would display such long subjects properly?
I just testet Outlook, and it seems difficult to show the mail co
Bjørnar Nielsen wrote:
>> That's what I was alluding at; I was assuming he meant that
>> the message would arrive intact with the entire subject line
>> without breaks or truncation.
>
> It does, but I can't write more than 256 chars in the subject-line. The
> subject is kept as a single line, no
Angus Robertson - Magenta Systems Ltd wrote:
>> I've uploaded a tiny buffered file stream class as well
>> as a simple test program. It is amazing fast when small
>> chunks are read/written. Seeking is slower than TFileStream :(
>
> I'll try in one of my applications, but it won't be until next we
>
> That's what I was alluding at; I was assuming he meant that
> the message would arrive intact with the entire subject line
> without breaks or truncation.
It does, but I can't write more than 256 chars in the subject-line. The
subject is kept as a single line, no splits. The subject is sen
On Oct 26, 2005, at 06:06, Arno Garrels wrote:
>>
>> So the subject arrives as one continuous line of 1000+ characters?
>> And
>> the SMPT server permits this? Strange. I'll take your word for it, as
>> I have no access to Outlook 2003 to test.
>
> Some mail servers reformat invalid headers an
> I've uploaded a tiny buffered file stream class as well
> as a simple test program. It is amazing fast when small
> chunks are read/written. Seeking is slower than TFileStream :(
I'll try in one of my applications, but it won't be until next week.
For the FTP server, I often have multiple PCs
DZ-Jay wrote:
> On Oct 26, 2005, at 04:18, Bjørnar Nielsen wrote:
>>> Outlook *does* indeed break long subject lines. Here's an
>>> example of a message I just sent using Outlook 2000:
>>
>> It does not when I test (Outlook 2003 SP1, but also with Norton
>> Antivirus,
>> dont know if this affects
On Oct 26, 2005, at 04:18, Bjørnar Nielsen wrote:
>> Outlook *does* indeed break long subject lines. Here's an
>> example of a message I just sent using Outlook 2000:
>
> It does not when I test (Outlook 2003 SP1, but also with Norton
> Antivirus,
> dont know if this affects this). Other lines a
Bjørnar Nielsen wrote:
>> Anyway, the RFC 821 says that the maximum line length
>> including is 1000 chars. If I use a subject that is
>> longer, and break the line at 74 with and tab, the
>> header-subject would be RFC-compliant, but the smtp-component
>> would crash.
>
> I guess I could use On
Hello,
I've uploaded a tiny buffered file stream class as well
as a simple test program. It is amazing fast when small
chunks are read/written. Seeking is slower than TFileStream :(
http://www.duodata.de/misc/bufstrm.zip
Compiled it with D5 and D7, supports 64 bit from D6 upwards.
I've been usin
> Anyway, the RFC 821 says that the maximum line length
> including is 1000 chars. If I use a subject that is
> longer, and break the line at 74 with and tab, the
> header-subject would be RFC-compliant, but the smtp-component
> would crash.
I guess I could use OnProcessHeader and split the
> Outlook *does* indeed break long subject lines. Here's an
> example of a message I just sent using Outlook 2000:
It does not when I test (Outlook 2003 SP1, but also with Norton Antivirus,
dont know if this affects this). Other lines are split but not the subject.
> > Anyway, TCustomSmtpClien
30 matches
Mail list logo
