@yuneta/gobj-ui 7.0.0 → 7.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +1 -1
- package/src/c_yui_treedb_topics.js +12 -0
package/package.json
CHANGED
|
@@ -1238,7 +1238,19 @@ function subscribe_treedb(gobj, topic_name)
|
|
|
1238
1238
|
}
|
|
1239
1239
|
|
|
1240
1240
|
/************************************************************
|
|
1241
|
+
* The counterpart of subscribe_treedb(), and NOBODY CALLS IT
|
|
1242
|
+
* today: a topic subscribed once stays subscribed for the life
|
|
1243
|
+
* of the view, and the whole set is released when the view (and
|
|
1244
|
+
* with it its transport) is destroyed. So there is no leak to
|
|
1245
|
+
* fix, and no caller to add on that account.
|
|
1241
1246
|
*
|
|
1247
|
+
* It is kept deliberately. It is the only place that knows the
|
|
1248
|
+
* exact shape the remote subscription was made with — the three
|
|
1249
|
+
* events, `__service__` and the `treedb_name`+`topic_name`
|
|
1250
|
+
* filter — and a remote unsubscribe only lands if it matches
|
|
1251
|
+
* the subscribe verbatim. Deleting it would not remove that
|
|
1252
|
+
* knowledge, it would move it to whoever needs it next, to be
|
|
1253
|
+
* rederived from the subscribe side and got right again.
|
|
1242
1254
|
************************************************************/
|
|
1243
1255
|
function unsubscribe_treedb(gobj, topic_name)
|
|
1244
1256
|
{
|