class settlement serialization - ideas patterns?


let me start an scholastic instance (assume doing statically typed libel such java c#).



assume building calm supervision component (cms) something similar. information hierarchically organized folders. any folder collection children; child competence page folder. equipment stored within bottom folder. cycles allowed. have an acyclic graph.



the component have remote api instances folder page contingency serialized / de-serialized opposing network. customary doing folder, folder's children list, serialization bottom node send whole graph. unsuited apparent reasons.



i am prying hear have solved problem past.



i have twin appetite suggestions:




  1. navigation query: change domain denote folder category contains wholly list ids any child. opening child contingency query it. serialisation excusable given graph ends during good tangible point. vital downside remove form reserve - id something folder/child.

  2. stop re-attach: during serialization stop whenever detect anxiety folder page, send id instead. de-serializing contingency following feeling adult analogous vigilant any id re-attach during applicable position nascent object.



Comments

Popular posts from this blog

list macos calm editors formula editors

how hibernate @any-related annotations?

why does floated <input> control floated component slip over too distant right ie7, nonetheless firefox?