Hi John,
If I understand you correctly, I could set up the web container so
that if Rife doesn't find a resource, it would look on the
filesystem? So I guess I could just have folder with the player
and skin files.
RIFE is installed like this by default. It runs as a servlet filter
and any request that comes in that can't be handled by RIFE will
automatically fall through to what ever filter is present in the
filter chain and ultimately to the servlet container itself and the
static files that are present in the web directory.
The thing that was missing was support for this in the content
management framework element that streams out the content to the
browser. Instead of deferring the request to the servlet container,
it forcibly displayed a "not found" status page.I have committed the
changes that were required for this deferring behavior and you will
be able to download it with tomorrow's snapshots.
Still not sure how that would work. So, let me think out loud
here... The URL for my "page" (Element) is:
/subsite/plan?planiId=1
So the Player Object will look for the player SWF and Skin files in
the same "directory," /subsite/FLVPlayer_Progressive.swf and /
subsite/farmSkin_large.swf. So I can create a directory structure
that mimicks the Rife URLs, and the container would try the Rife
filter then, er, something else that looks for static resources on
the filestytem. Wouldn't that work?
Exactly! You will be able to do that with the next snapshot.
The URL for the actual movie, which would be streamed from the CM
subsystem, can be (at least) relative to the "page," e.g.: ../
content/video/1/movie.flv--so the content management URL would work
fine *except* that I need the .flv added. Can one specify that
URLs that match a certain expression should have a suffix
appended? Or something?
The way to do this is by stripping away the extension. So when you
generate the URL, you append the extension or already include it into
the template after the value tag that will contain the URL. Then,
instead of using the standard ServeContent element, you extend its
Java implementation and override the filterPath method. There, you
can perform any modification to the path before the content is looked
up in the content store.
Hope this helps,
Geert
--
Geert Bevin
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.org
Music and words - http://gbevin.com
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users