[Zookeeper-developer] [ zookeeper-Bugs-1967467 ] zookeeper_init doc needs clarification

[SourceForge.net <no...@so...>]

Bugs item #1967467, was opened at 2008-05-19 15:05
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1008544&aid=1967467&group_id=209147

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: c client
Group: 3.0.0
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Patrick Hunt (phunt)
Assigned to: Andrew Kornev (akornev)
Summary: zookeeper_init doc needs clarification

Initial Comment:
the zookeeper_init document needs to be clarified on two points:

1) that when it returns the client may/maynot have an active session on the server. init call is asyncronous - notification comes back through the watcher when the session is established.

2) this section seems to be wrong. If a client id is invalid (say you pass clientid 1 on a new zk instance) a new session is not created, rather the client's zk handle (when later used) complains that the session is expired. 

 * \param clientid the id of a previously established session that this
 *   client will be reconnecting to. Pass 0 if not reconnecting to a previous
 *   session. If the session timed out or the id is invalid, a new
 *   session will be automatically generated. Clients should check the actual
 *   session id by calling \ref zoo_client_id. 

Notice that the server message (console) is also misleading - it seems to indicate that the session was reestablished, but in reality is has not. A more clear log message on the server would help here.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1008544&aid=1967467&group_id=209147