Reply to thread

Message

<blockquote data-quote="MJGraf" data-source="post: 1118743" data-attributes="member: 17886"><img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /> For that exact reason I have already extended the <a href="https://github.com/MediaPortal/MediaPortal-2/blob/master/MediaPortal/Source/Core/MediaPortal.Common/MediaManagement/ImporterWorkerMessaging.cs#L80" target="_blank">ImporterWorkerMessaging.MessageType,ImportProgress</a>, which in the current new ImporterWorker already carries much more information than before (see link above for explanation).But as Morpheus already mentioned, for Server MediaSources, this message is currently only sent within the MP2 Server process and the MP2 Clients cannot see it. I do not think that it is very complicated to propagate this message to the client, because we already do exactly that with the ImporterWorkerMessaging.MessageType.ImportStarted and ImporterWorkerMessaging.MessageType.ImportCompleted messages (via ContentDirectoryMessaging and the ContentDirectory - we could even use the already present state variable &quot;CurrentlyImportingSharesChangeCounter&quot; for the notifications). These messages are currently responsible to notify a client when an import has started and finished and are used to display exactly that in the MediaSources overview page.The only thing we really need to test is whether this causes too much network traffic. The ImportProgress message is currently sent when an import starts, finishes and in between every 100 imported MediaItems (see link above). I thought that this is a good value for &quot;local messages&quot;. If it is too much for propagating over the network, we may need to restrict the propagation of these messages to every 5th or 10th local message...Michael</blockquote>

[QUOTE="MJGraf, post: 1118743, member: 17886"] :) For that exact reason I have already extended the [URL='https://github.com/MediaPortal/MediaPortal-2/blob/master/MediaPortal/Source/Core/MediaPortal.Common/MediaManagement/ImporterWorkerMessaging.cs#L80']ImporterWorkerMessaging.MessageType,ImportProgress[/URL], which in the current new ImporterWorker already carries much more information than before (see link above for explanation). But as Morpheus already mentioned, for Server MediaSources, this message is currently only sent within the MP2 Server process and the MP2 Clients cannot see it. I do not think that it is very complicated to propagate this message to the client, because we already do exactly that with the ImporterWorkerMessaging.MessageType.ImportStarted and ImporterWorkerMessaging.MessageType.ImportCompleted messages (via ContentDirectoryMessaging and the ContentDirectory - we could even use the already present state variable "CurrentlyImportingSharesChangeCounter" for the notifications). These messages are currently responsible to notify a client when an import has started and finished and are used to display exactly that in the MediaSources overview page. The only thing we really need to test is whether this causes too much network traffic. The ImportProgress message is currently sent when an import starts, finishes and in between every 100 imported MediaItems (see link above). I thought that this is a good value for "local messages". If it is too much for propagating over the network, we may need to restrict the propagation of these messages to every 5th or 10th local message... Michael [/QUOTE]

Verification