{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 SAY GOODBYE 的问题《NTFS Junctions vs. Symbolic Links (for directories》','https://www.manongdao.com/q-1324324.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
From a high-level standpoint (meaning only worrying about the results and the interface, not the implementation), what is the difference in behavior, if any, between an NTFS reparse point that points to a directory and a symbolic link that points to the same directory?
Are they resolved at the same level in the stack, or is it possible for one to be unresolvable at a certain time when the other one can be resolved (e.g. at boot)?
(I'm aware that symbolic links can also work for files, but I'm asking about the directory difference here.)
It is known that in network symbolic links are resolved on clients, while junctions are resolved by server. One can suggest, that junctions are more "invisible" for users.