2 Dec
2011
2 Dec
'11
7:35 p.m.
However pondering the problem I've prototyped a
solution in which PRFile
have a custom view component "PRFileView" which responds with it's
associated PRFile file directly, rather than delegating
to MAFileModelHandler. The logic is that, by default, PRFile>>#url responds
with a fully qualified path to itself within the pier structure
e.g. /pier/template/style.css then PRFileView>>#initialRequest checks the
request to see if it matches the mime-type of it's associated PRFile's
mime-type, if so it will respond true to PRFileView>#isFullResponse and
serve the file directly in PRFileView>#respondUsing:
The problem is that like this you cannot easily navigate to the
resource anymore.
Lukas
--
Lukas Renggli
www.lukas-renggli.ch