backend.jar errors.

[sleeper_service]

Strange. Ping-pong should be handled automatically in the backend regardless of anyone being connected to the frontend. Could this be a network issue? If your ircd is on the same host, probably not.

the ircd is at a friends house not too far away, he's got the same isp I do. I've got an always on connection, as does he, I'm logged into the server with pidgin, and it's not dropping. (he runs a little private server for a few friends, much like you're doing).

interestingly enough, it's not dropping the connections at the same time with his server and yours.

if you think it'd help, I can snoop the network traffic and see if there's anything that looks out of place... where'd I put my wireshark. *ponder*

[fox]

Maybe tt-irc is not doing some keep alive thing or something. My ircd and tt-irc are on the LAN so it never been a problem here.

[sleeper_service]

Maybe tt-irc is not doing some keep alive thing or something. My ircd and tt-irc are on the LAN so it never been a problem here.

Ok, so I installed a copy of ircd-hybrid on a remote linux server, and changed the ping frequency in backend.jar, and it has the same timeout issues, the same version of ircd-hybrid on the local network works.

also, I'm confused about something I thought that ttirc would do that it doesn't seem to be doing, unless I've got something set wrong.

I see that when the backend is running and logged in, it's capturing to the database, but when the web/android client logs in, it doesn't get a display of the messages that were logged. am I doing something wrong, is that feature not working, or is it by design that those messages just don't ever show up, in which case, why keep 12 hours of them by default?

*scratching head*

[fox]

When you log in, you get some limited backlog of messages based on get_initial_last_id() - I think it's last 50 - to prevent initial flood. If you were logged in already and your device went to sleep, you get the entire log that happened since last received message. So if you want to get everything that happened (with caveats, the scrollback buffer is limited because web browsers start getting unbearably slow otherwise, so techniclaly it's last 200 lines or so - you can tweak that too, I guess), don't log out from tt-irc before you put your PC to sleep.

You can also change the amount of stuff you initially receive in functions.php.

[sleeper_service]

how about an enhancement request?
when you log in, it starts showing stuff from 10 minutes before you logged out last, and you can scroll down to present?
either that, or a button to pull more history?

[fox]

Time based is how it was before, I changed it to be based on line-numbers because it's more predictable regardless of channel activity. You can change it in the function named above if you know basic SQL.

Button to pull more history, I dunno. It's all designed to only go forward based on IDs, not back.