I've updated my ResourceLoadAction so that it optionally will save the resource stream data (as a string) in your session/request with a given attribute name.
Technically speaking now, have you considered using output modules to indicate where the resource should be loaded? This should be more versatile than a fixed choice between session and request.
Had anybody considered writing some dom:/ pseudo protocol to save/retrieve DOM fragments to/from request / session / application context?
We have a Read/WriteDomSessionTransformer (for which Andrzej provided also a patch) doing this stuff. You mean replacing them with a dom pseudo protocol for simplicity and transparency? Sound good.
Joerg
