On Thursday, March 6, 2014 at 3:30:35 PM UTC-6, Stefan Adams wrote:
>
>
>
>
> On Thu, Mar 6, 2014 at 1:24 AM, sri <[email protected] <javascript:>> 
> wrote:
>
>> What should be done about conflicting types?  e.g. dwg is 
>>> application/x-acad, image/x-dwg, and image/vnd.dwg
>>>
>>
>> Just like "xml".
>>
>>      
>> https://github.com/kraih/mojo/blob/master/lib/Mojolicious/Types.pm#L30
>>
>
>  Thanks, sri! I'll do that!  Because alternatives are only used for 
> detection, do all valid options need to be ordered in anyway?  That is, is 
> it necessary that application/xml be listed before text/xml?
>
> I trust then that everything else is OK with the plugin?
>
> Oh, I didn't consider... What happens when you register a type that's 
> already registered? That is, core registers xml and certainly the plugin 
> does too. Is it important to skip already registered types, or, because 
> it's running only on MIME::Types, it's just going to redefine it to the 
> same thing so it doesn't matter that it redefines what what defined in core?
>

I think I've addressed all these issues.  Multiple mime types per extension 
and a test file to go along with it.  Any suggestions welcome, but I think 
this is a final working product 
<https://github.com/s1037989/Mojolicious-Plugin-MimeTypes>.  This is what 
you had in mind, right sri?

-- 
You received this message because you are subscribed to the Google Groups 
"Mojolicious" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/mojolicious.
For more options, visit https://groups.google.com/d/optout.

Reply via email to