[
https://issues.apache.org/jira/browse/WAVE-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ali Lown resolved WAVE-127.
---------------------------
Resolution: Invalid
First wave is no longer auto opened.
> WIAB client's network connection logic is racy
> ----------------------------------------------
>
> Key: WAVE-127
> URL: https://issues.apache.org/jira/browse/WAVE-127
> Project: Wave
> Issue Type: Bug
> Priority: Minor
>
> The behaviour of auto-open of the first wave in a wave list (perhaps we
> should just remove that behaviour, once someone can reverse engineer the
> index wave code) can trigger socket communication before the connection is
> established.
> I have a simple fix ready, which just ignores list-selection events if the
> socket is not connected, but there are a number of fixes required. The
> proper fix involves:
> * being clear that the network's DISCONNECTED state means transient
> disconnection; i.e., the client will try to reconnect if that state occurs.
> A terminal CLOSED state should be added if we ever want the client not to
> reconnect.
> * adding in backoff for reconnection attempts.
> * client's socket layer should queue client messages (rather than die) when
> in a transient disconnected state. Should still die if the client tries to
> send a messsage in a CLOSED state, if that state gets added.
> ---
> Issue imported from
> http://code.google.com/p/wave-protocol/issues/detail?id=126
> Owner: [email protected]
> Label: Type-Defect
> Label: Priority-Medium
> Stars: 1
> State: open
> Status: Accepted
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
