I took the lack of answers as a silent agreement so this change has alread been 
done and committed as part of MH-9210. Please also see review 
http://opencast.jira.com/source/cru/CR-MH-485 that Greg created for the big 
changeset of which this modification is part of.

Christoph


Am 04.10.2012 um 00:02 schrieb Tobias Wunden <[email protected]>:

> Hi Christoph,
> 
> as far as I remember there was no special thougth with respect to mutable vs. 
> immutable behind the implementation of the MimeTypes class (maybe there 
> should have been :-) So as long as nobody else is chiming in, feel free to do 
> what you think is best.
> 
> Tobias
> 
> On 27.09.2012, at 15:01, Christoph Drießen <[email protected]> wrote:
> 
>> Working on ticket http://opencast.jira.com/browse/MH-9210 I found myself 
>> wondering about the mutable nature of the MimeType class. MimeType is such a 
>> simple data holder that there is no use to it. In fact it's a drawback. I 
>> don't want to open the discussion about mutable state in general -- since I 
>> assume everyone is familiar with the issues that mutable state causes 
>> especially in a distributed, parallel system like Matterhorn -- but I'd like 
>> to ask if anyone has any objections to making it immutable.
>> 
>> Thanks,
>> Christoph
>> 
>> 
>> _______________________________________________
>> Matterhorn mailing list
>> [email protected]
>> http://lists.opencastproject.org/mailman/listinfo/matterhorn
>> 
>> 
>> To unsubscribe please email
>> [email protected]
>> _______________________________________________
> 
> _______________________________________________
> Matterhorn mailing list
> [email protected]
> http://lists.opencastproject.org/mailman/listinfo/matterhorn
> 
> 
> To unsubscribe please email
> [email protected]
> _______________________________________________

_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________

Reply via email to