Connection closed

[pilot]

Every time I connect to Meteor as: fsockopen(my_server, 4671,....), in
order to send a ADDMESSAGE,
I get the notice: ... notice Connection closed: Connection reset by
peer
and no message reach the client.

Please, have any suggestions to this?

Thanks

[Kevin Peno]

Is meteor running on windows by chance?


Kevin Peno
W: 425.582.8139
C: 425.408.1094
ke...@metalaxe.com
--from my mobile device--

> --
>
> You received this message because you are subscribed to the Google
> Groups "meteorserver" group.
> To post to this group, send email to meteor...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/meteorserver?hl=
> .
>
>

[pilot]

Thank you for yr response.

Meteor is running on Linux.

It is running last year successfully.
This problem created when I decided to open a new channel and send
ADDMESSAGE not from the same server, where Meteor is installed, but
from another server (intranet - no firewall).
Could be a problem?

Thanks

On 18 Νοέ, 19:22, Kevin Peno <kevinp...@gmail.com> wrote:
> Is meteor running on windows by chance?
>
> Kevin Peno
> W: 425.582.8139
> C: 425.408.1094
> ke...@metalaxe.com
> --from my mobile device--
>

[Lagos, Ioannis]

Thank you for yr response.

Meteor is running on Linux.

It is solved!!!
There was an error (syntax) to the sending string!

I have also another question.

To a channel A are joined many clients. When a new client joins to a
channel for a first time, it receives all the messages stored for this
channel. That's fine, but when next time it joins the same channel must
not receive any of the old message, until a new one message comes up.

Have I to deploy a new functionality for this?

Thanks a lot

[Kevin Peno]

You would instruct the meteor js client to not get any messages. There is a parameter related to the number of old messages to get from the server.

Kevin Peno
E: kevi...@gmail.com
C: 425.408.1094