Hi Xavier, I guess this is already possible with the Directory class, you just need to store the video as a separate file for each format, with the proper file extension. Content negotiation would do the rest, eventually adding the extension at the end of the URI if the "Accept" header can't be modified.
But maybe your point is to store only the core video content as dynamically generate the video container? Best regards, Jerome -- Restlet ~ Founder and Technical Lead ~ http://www.restlet.org Noelios Technologies ~ http://www.noelios.com -----Message d'origine----- De : Xavier Mehaut [mailto:[email protected]] Envoyé : samedi 28 août 2010 06:12 À : [email protected] Objet : Re: More RIAP Features? hello jerome i don t know if this proposition falls into this category, but it could be nice to have a video resource with several representations, eg h264 into several video container, or mpeg4 or webm, ... so we could have easily a http video server with restlets like the one we may have with red5 for instance regards xavier Envoyé de mon iPhone Le 28 août 2010 à 01:42, Jerome Louvel <[email protected]> a écrit : > Alex, > > Long delay in my replies lately, but not due to lack of interest. You are > making great suggestions. I've taken note of them in this RFE: > > "Enhance RIAP scheme" > http://restlet.tigris.org/issues/show_bug.cgi?id=876 > > Maybe a better way to solve this would be to facilitate the > nesting/composition of applications and the usage of a relative "parent" RIAP > authority. See also this related RFE: > > "Add Composite parent class" > http://restlet.tigris.org/issues/show_bug.cgi?id=1092 > > Could you describe your use case in term of domain name/virtual host more > precisely so we have something more concrete to think about? > > Best regards, > Jerome > -- > Restlet ~ Founder and Technical Lead ~ http://www.restlet.org Noelios > Technologies ~ http://www.noelios.com > > > > > -----Message d'origine----- > De : [email protected] [mailto:[email protected]] De la part de > Alex Milowski Envoyé : jeudi 3 juin 2010 15:43 À : > [email protected] Objet : More RIAP Features? > > I've been thinking more about how I'd like to use and/or limit the use of > RIAP, especially in the context of hosted applications where you are trying > to limit access to the resources used by each. Here's a couple of things I'd > like to be able to do: > > 1. I'd like to restrict attached resources/restlets to a specific virtual > host, much like an internal router on the component, so that I can > attach internal applications that are not exposed to the outside > world. > > 2. I'd like to scope access within those hosts to specific application > and all their descendant/used applications. > > My use case is simply that when I startup and include a service like an eXist > XML database, I don't really want to attach it to the component as every > application would have access to the embedded database. I'd associate that > database, via RIAP, with the host or some particular part of the host's > overall application. > > I believe I can currently do some this attaching a guard that only allows > access over RIAP from certain clients. Of course, that may require knowing > that the request will tell me who the user of the RIAP is in such a way that > I can say "this is my application". I'm not sure I can always get that and > so it may only get me part of the way there. > > --Alex Milowski > > ------------------------------------------------------ > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId > =2616443 > > ------------------------------------------------------ > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId > =2652215 > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2652282 ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2653434
