Early messages #2

Closed
opened 2014-04-26 09:27:20 +00:00 by thorsten · 4 comments
thorsten commented 2014-04-26 09:27:20 +00:00 (Migrated from devops.tsommer.org)

There is a problem with early ICCC messages, because the listener cache is not yet filled. Therefore, all these early messages are rejected!

There is a problem with early ICCC messages, because the listener cache is not yet filled. Therefore, all these early messages are rejected!
thorsten commented 2014-06-04 12:17:08 +00:00 (Migrated from devops.tsommer.org)

Should be okay now! The init function is now building up the whole cache before returning.

Should be okay now! The init function is now building up the whole cache before returning.
thorsten commented 2014-06-05 09:25:35 +00:00 (Migrated from devops.tsommer.org)

It is not okay: The new problem is, that all local ICCC commands are disabled by the last shutdown event. Therefore, the correct loaded cache is still empty! It would be necessary, that also all commands are activated before the init event is returning or at least, that the cache gets loaded after all commands are active again.

It is not okay: The new problem is, that all local ICCC commands are disabled by the last shutdown event. Therefore, the correct loaded cache is still empty! It would be necessary, that also all commands are activated before the init event is returning or at least, that the cache gets loaded after all commands are active again.
thorsten commented 2014-06-05 11:18:01 +00:00 (Migrated from devops.tsommer.org)

Another problem for early messages: Until the web server is not up and running, it is not possible to deliver these messages.

Another problem for early messages: Until the web server is not up and running, it is not possible to deliver these messages.
thorsten commented 2014-06-05 11:48:21 +00:00 (Migrated from devops.tsommer.org)

Done. The sender is able to wait until the web server is up and ready. Early messages are working fine now! All tests passed :)

Done. The sender is able to wait until the web server is up and ready. Early messages are working fine now! All tests passed :)
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Go/Ocean#2
No description provided.