[Opensim-dev] Serving textures in different formats

[Justin Clark-Casey]

I agree with David, B seems a nicer mechanism to me as it makes use of existing content negotiation mechanisms. 
However, interestingly a quick Google does not reveal consensus on the topic - I was expecting B to be the clear winner.

On 08/12/10 15:48, David W Levine wrote:
> I strongly prefer B. It opens the door for genuine content negotiation in a web consistent and appropriate mechanisms.
>
> - David
>
>
> opensim-dev-bounces at lists.berlios.de wrote on 12/08/2010 10:36:42 AM:
>
>  > From:
>  >
>  > Diva Canto <diva at metaverseink.com>
>  >
>  > To:
>  >
>  > opensim-dev at lists.berlios.de
>  >
>  > Date:
>  >
>  > 12/08/2010 10:43 AM
>  >
>  > Subject:
>  >
>  > [Opensim-dev] Serving textures in different formats
>  >
>  > Sent by:
>  >
>  > opensim-dev-bounces at lists.berlios.de
>  >
>  > So far, all textures in OpenSim are stored and served as jp2. However,
>  > some viewers can't use jp2. Example: Unity3d, for the time being. I
>  > would like to improve the GetTexture cap service by adding the ability
>  > for it to make conversions on the fly depending on extra data provided
>  > by the caller.
>  >
>  > There are two ways of doing this. Which one do people prefer?
>  >
>  > A) Add an extra query parameter:
>  > http://foo.com/GetTexture/?texture_id=<uuid>&format=<format>
>  >
>  > B) Use the Accept and Content-Type headers appropriately.
>  > The request might have
>  > Accept: image/png, image/jp2
>  > And the response might have
>  > Content-Type: image/png
>  >
>  > Diva / Crista
>  >
>  > _______________________________________________
>  > Opensim-dev mailing list
>  > Opensim-dev at lists.berlios.de
>  > https://lists.berlios.de/mailman/listinfo/opensim-dev
>
>
>
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/opensim-dev


-- 
Justin Clark-Casey (justincc)
http://justincc.org
http://twitter.com/justincc