now icon indicating copy to clipboard operation
now copied to clipboard

Handling server reset (more) gracefully

Open scriby opened this issue 12 years ago • 1 comments

Most things seem to work fairly well when the now server a client is connected to gets reset. The clients reconnect and for the most part continue on where they left off.

I've noticed one odd behavior, though.

  • If the client has a variable set in the now namespace, it won't get "unset" if the server doesn't have it defined
  • If the client has an array set in the now namespace, and the server defines the same one and adds items to it, the client appends them instead of resetting the array

For my purposes, the correct outcome would be for the client's now variables to get reset and re-sync'd exactly with the server's. I understand that this is kind of tricky because the client may have set their own now variables which aren't recorded anywhere else, but I don't use that feature :)

scriby avatar Jan 22 '13 01:01 scriby

Also, sorry to spam you with issues. I don't really expect you to address these, but I think it's helpful for people to know what some of the limitations are when adopting this library.

scriby avatar Jan 22 '13 01:01 scriby