Hello,
fixed my Smtp problem not by specifiying UTF8 as charset and using
AnsiToUTF8
For the mail body and subject line. Works correct as it seems.
Greetings
Markus
ebm-papst Mulfingen GmbH & Co. KG
Sitz der Gesellschaft: Bachmuehle 2, D-74673 Mulfingen
Kommanditgesellschaft Sitz Mulfingen:
Hello,
Thanks for the information in the first place.
> >
> > Any hints for me how to do this the correct way? e.g. find out the
> > user's charset and use that? Or sending UTF8? (does this work with
all
> > mail clients?)
>
> UTF-8 is the charset to use, that should work with all common mail
Hello,
I've some big problems with the telnet components, the biggest one being
the lack of documentation.
What I want to do is the following:
1. start a telnet session (that one works)
2. have a list of commands
3. loop through the list and carry out one command after the other
4. display th
Hello,
I've got the following problem and look for the real cause:
(don't know yet whether TWSocket is involved or not, but looks like)
I've a dll with a message pumping thread and at least one sending
TWSocket and one seperate receiving TWSocket.
The very same DLL provides also other communica
Hello,
> -Ursprüngliche Nachricht-
> Von: Fastream Technologies [mailto:[EMAIL PROTECTED]
> Gesendet: Montag, 27. März 2006 12:35
> An: ICS support mailing
> Betreff: Re: [twsocket] DLLs and Threads
>
>
> Hello Markus,
>
> I have just read the below message you sent and you really
> ne
Hello,
it seems to work okay right now (not yet creating any sockets) but
one thing is still sub-optimal, my message pump.
You advised me to use GetMessage, but that creates the problem
that the thread won't terminate gracefully if .terminate.
SendMessage could solve it if it wouldn't require a w
Hello,
friday afternoon I outlined my new approach.
Before implementing it I'd like to know if packing all creating and closing
stuff in a dedicated thread (one for all sockets) with a message pump
is okay (should work if implemented with some care). Is it okay now?
Did I understand the concept c
Hello,
sorry, pressed the wrong button.
I had changed the code now so that the socket is created within the context of
the thread
(veryfied by GetCurrentThreadID) at start of execute and closing is initiated
at the end of
execute (same threadID). In the communication DLL (not the one which co
Hello,
I had changed the code now so that the socket is created within the context of
the thread
(veryfied by GetCurrentThreadID) at start of execute and closing is initiated
at the end of
execute (same threadID). In the communication DLL (not the one which contains
the thread but the one who
> -Ursprüngliche Nachricht-
> Von: Francois Piette [mailto:[EMAIL PROTECTED]
> Gesendet: Freitag, 3. Februar 2006 11:21
> An: ICS support mailing
> Betreff: Re: [twsocket] closing socket socket
>
>
> > So I called DetachThread before Attach Thread, but now I get the
> > exception that t
> Hello Markus,
>
> > Okay, exception can be ruled out, the shutdown call is within try /
> > except and
> > I have a output in the except clause showing the exception.
> This doesn't
> > fire.
>
> There is something wrong that we cannot see. Consider one of your
> previous mails:
>
> > - outp
Hello,
after moving the creation of the sockets in the execute method of the
thread which sends and initiates the closing of the communication
channel
the thing closed like a charm!
Now there is only the problem if the communication doesn't close and the
communication dll tries to close the stil
Hello again,
one more thought:
after calling shutdown, do I need to poll windows messages?
If yes, how to do it properly and in such a way that it only
polls as long as needed?
At the time the socket is closed there is another thread which
only polls messages. Is this enough?
Greetings
Marku
Hello,
I tried something different now, but without success yet.
After looking at which thread ids where involved I got the following
results:
- the socket is created in one thread
- the other thread is sending data over the socket, which works like a
charm
- the other thread then requests a clos
Hello,
> Hello Markus,
>
> > I put some debug output in my OnSessionCLosed handler, it
> doesn't seem to be called.
> > But I haven't yet debugged.
>
> See my other reply. If it is not fired, then eather ShutDown did not
> work because of some exception error, or eather the message
> pump of t
> Hello Markus,
>
> Seems you don't get the Event-driven way of programming, why a loop of
> 100ms that seems to do nothing with event it could receive ?
>
> HM> - output a debug message to eventlog
> HM> - socket.shutdown(1);
> HM> - output a 2nd message to eventlog
> HM> - do this:
> HM> t:=G
Hello,
> Hi Marcus,
>
> I've been following your problem and I believe that the
> problem you have
> is because you are trying to use a dll with only a little
> multi-threading experience. One of the reasons people avoid threads is
> that it requires a lot of reading, development time,
> experi
Hello,
I put some debug output in my OnSessionCLosed handler, it doesn't seem to be
called.
But I haven't yet debugged.
Greetings
Markus Humm
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at ht
Hello,
I did some changes now (I will onl make changes to my communication dll
which don't affect the other communication methods).
I derrived a descendant from TWSocket which implements the OnSessionClosed
method
and overrides create to assign my OnSessionClosed variant to the property.
In my
> >> Humm, Markus wrote:
> >>> The dll using that communication dll has one thread per socket
> >>> (max. at most 10). Freing the socket is requested by this dll
> >>> when it's execute method terminates.
> >>
> >> And the
> > > And the socket has been _created in method execute as well?
> > > How do you achieve that client sockets run in the client thread
> > > if not using ThreadAttach/ThreadDetach?
> > Hm, no it is created before execute. And no thread attach/detach is used.
> > It works so far until the point wh
> -Ursprüngliche Nachricht-
> Von: Arno Garrels [mailto:[EMAIL PROTECTED]
> Gesendet: Mittwoch, 1. Februar 2006 12:10
> An: ICS support mailing
> Betreff: Re: [twsocket] Problems with TWSocket.close and DLL
>
>
> Humm, Markus wrote:
> > The dll using
> -Ursprungliche Nachricht-
> Von: Dod [mailto:[EMAIL PROTECTED]
> Gesendet: Mittwoch, 1. Februar 2006 12:02
> An: ICS support mailing
> Betreff: Re: [twsocket] Problems with TWSocket.close and DLL
>
>
> Hello Markus,
>
> Why do you use one thread per socket ? TSWocket is event driven
Hello,
to the socket hanging on close.
There are different threads involved.
The communication dll has one thread which only polls messages.
That one shouldn't be the problem.
The dll using that communication dll has one thread per socket
(max. at most 10). Freing the socket is requested by this
Hello,
I'm writing a application in D2006 and build a communication dll for it.
The communications dll encapsulates different communication methods (for USB,
ethernet...).
Ethernet communication is done via ICS TWSocket, the version included on the
partner cd.
The DLL has a data module which ha
Hello,
solved the problems now by using the version from the D2006 Partner DVD.
But I'm still curious about the things found in the downoad from the ICS
website.
I was under the ICS section when I downloaded it - I didn't use the "latest
version"
link in the upper left corner of the website.
Hello,
today I tried to install ICS under Delphi 2006 until now without success.
1. you change constants there whih isn't allowed anymore without
setting some compiler switch ($J+), that can be changed under the project
settings, okay.
2. GWSockCritSect ist not found in wsocket.pas in line
27 matches
Mail list logo