Reply to thread

Message

<blockquote data-quote="MJGraf" data-source="post: 1149269" data-attributes="member: 17886">Understood - that's what I thought.So thesea are basically two different use cases:<ul>
<li data-xf-list-type="ul">Waking MP2-Server when a client starts (this one should be easy and can be handled by a client plugin)</li>
<li data-xf-list-type="ul">Waking another computer when someone tries to access a computer via a NetworkNeighborhoodResourceAccessor. This is the more complicated one.<ul>
<li data-xf-list-type="ul">It can happen on client and server (on the server-side: how do we handle nightly imports?)</li>
<li data-xf-list-type="ul">In general, the functionality should be contained in the NetworkNeighborhoodResourceAccessor / -Provider, as it only affects MediaSources based on these Accessors. But it somehow has to happen &quot;transparently&quot; so that a caller doesn't even notice what's happening. So we basically need something in each method of the NetworkRA, which (a) first tries to access the resource - if it works all is fine and (b) if this does not work, try to wake up the computer, wait a bit and then try to access again. If it works now, all is fine. If not, finally fail...</li>
</ul></li>
</ul>After all, I think ít is best to have only one plugin for client and server. Functionality for the first bullet-point above is only activated if the plugin starts in a client (and the server is not on the same computer). Besides that it just provides the functionality that the NetworkRA-Plugin can use to do its job from the second bullet-point above.Is there anything else we need to take care of?I only had a short look into the MP1-wiki for the implementation there and there are some more things MP1 takes into account, such as sending the WoL package in certain intervalls to keep the remote computer running. Is that e.g. something we need?</blockquote>

[QUOTE="MJGraf, post: 1149269, member: 17886"] Understood - that's what I thought. So thesea are basically two different use cases: [LIST] [*]Waking MP2-Server when a client starts (this one should be easy and can be handled by a client plugin) [*]Waking another computer when someone tries to access a computer via a NetworkNeighborhoodResourceAccessor. This is the more complicated one. [LIST] [*]It can happen on client and server (on the server-side: how do we handle nightly imports?) [*]In general, the functionality should be contained in the NetworkNeighborhoodResourceAccessor / -Provider, as it only affects MediaSources based on these Accessors. But it somehow has to happen "transparently" so that a caller doesn't even notice what's happening. So we basically need something in each method of the NetworkRA, which (a) first tries to access the resource - if it works all is fine and (b) if this does not work, try to wake up the computer, wait a bit and then try to access again. If it works now, all is fine. If not, finally fail... [/LIST] [/LIST] After all, I think ít is best to have only one plugin for client and server. Functionality for the first bullet-point above is only activated if the plugin starts in a client (and the server is not on the same computer). Besides that it just provides the functionality that the NetworkRA-Plugin can use to do its job from the second bullet-point above. Is there anything else we need to take care of? I only had a short look into the MP1-wiki for the implementation there and there are some more things MP1 takes into account, such as sending the WoL package in certain intervalls to keep the remote computer running. Is that e.g. something we need? [/QUOTE]

Verification