see for example Image that one can old an Resource directly to make a session relative resource so yes resources can be serialized
On Fri, Mar 7, 2008 at 5:31 PM, Kaspar Fischer <[EMAIL PROTECTED]> wrote: > Johan, thanks a lot for your explanations! > > On 07.03.2008, at 15:47, Johan Compagner wrote: > > > do you need a transaction around the resource when only the > > lastModifiedTimeStamp is ask for? > > Yes, unfortunately. > > > is your resource really cachable? > > I am writing a WebResource that returns files from an external content > repository. So yes: the resource should be cached by the browser and > yes, I do have a lastModifiedTimeStamp. > > Or did you ask because I am using WebResource and not > DynamicWebResource? > I thought I am going to use WebResource as the content repository > (Alfresco, > in my case) probably already does some (server-side) caching and > DynamicWebResource would add another level of server-side caching > (right?). > > > head request must be really fast because the happen a lot > > and you should not be loading so much then > > > > So you just have to see if you can create a resourcestream that only > > has the > > right timestamp > > Okay, got it. > > Btw, is there a reason why WebResources are serializable? Are they > ever serialized? > > Thanks, > Kaspar > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
