Continue on this one please, Thanks for your precious help

Tech-Archive recommends: Speed Up your PC by fixing your registry



The two classes are for my common DLL between the server and the client.
When I'm talking about server in my previous message I meant the Chatter
class (because this instance is run on the server) and about client I meant
the Client class. Both are Singleton classes.

The configuration file is used in the Client class. This kind of setup allow
me to change the address without compiling again. Unless you tell me this is
a bad way to do it, I leave it like this.

My Notifier program is using this DLL via the Client.Send method.

--

Au plaisir,
Jonathan Boivin
---
Courriel : jonathanboivin@xxxxxxxxx
CyberInternautes : http://www.cints.net
Téléphone : 514-779-1129
"Jonathan Boivin" <djon@xxxxxxxxxxxxxxxxxxxx> a écrit dans le message de
news: OkZUBzM3GHA.3364@xxxxxxxxxxxxxxxxxxxxxxx
Hi people !

I used a remoting chat already built using events and a singleton object
on the server.

The events work fine, but not the method calling each time to send a
message.

When I call the send method and when it bugs (i have trace on the client &
server side), I can see my client trace but not the server trace. Let me
explain you a little bit more what is really strange.

I have two types of client (my principal and the notifier). I am currently
talking about the notifier. This notifier is a little and really simple
app which is used to send a single message to my principal clients via
other sources (like the DB). The notifier sends at first a hello message
and then, the message to forward.

The problem is happening when the message to forward is being sent. Which
means here that the hello message was sent correctly, but not the other
one. Weird hey ?

I joined a debug trace file. Here is a little explanation about it :
- When you see 'by 1' it represents a message received or sent by my
principal client.
- When you see 'by #' which # is not 1, it represents a message sent by
the notifier program.
- The trace 'Sending message by' is located on the client side, which
after this you should see a line + SomeOne said: something + a line (the
important keyword here is 'said:') (this trace is located on the server
side).
- The trace 'Receiving message by' is located on the client side.
- There is multiple trys in this debug file, there all good except one. A
try starts by 'Entered WaitForEndDB by' and ends by 'Quitting WaitForEndDB
by'.
- Search for 'Waiting 849 by 1' to get to the BUGGING part. (the number
849 is resent, but this was done manually to debug my principal client).
Here you can see the trace of sending hello on client and server side, but
we only see the sending of the number on the client side and not server.
- Search for 'Waiting 841 by 1' to get to a FUNCTIONAL part.

Thanks for looking at my problem and don't hesitate to ask other questions
if you don't understand something,
Jonathan Boivin
---
Courriel : jonathanboivin@xxxxxxxxx
CyberInternautes : http://www.cints.net




.



Relevant Pages

  • Re: What doesnt lend itself to OO?
    ... >> proxy and instructs the server to constuct the real object. ... rather than client code. ... If 'clock' is instantiated in the server, ... > for the server interface at the OOA level. ...
    (comp.object)
  • This is going straight to the pool room
    ... or not the client has privilege to do what they're trying to do, ... The server environment is this: ... 3GL User action Routines that Tier3 will execute on your behalf during the ... Routine Name: USER_INIT ...
    (comp.os.vms)
  • [Full-Disclosure] R: Full-Disclosure Digest, Vol 3, Issue 42
    ... Full-Disclosure Digest, Vol 3, Issue 42 ... SD Server 4.0.70 Directory Traversal Bug ... Arkeia Network Backup Client Remote Access ...
    (Full-Disclosure)
  • Re: What doesnt lend itself to OO?
    ... > rather than client code. ... no way to do that without also touching the object with clock semantics ... will not encapsulate both clock semantics and network semantics. ... The server can do whatever it wants ...
    (comp.object)
  • RE: ProtocolError?
    ... If I just do a simple TCP trace I get: ... Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client ... WWW-Authenticate: Negotiate ... WWW-Authenticate header field that the Web server is not configured to accept. ...
    (microsoft.public.dotnet.framework.aspnet.webservices)