I have an blurry idea of an approach for handling transient documents generated in loop, but covers narrow usage like graphs and images used immediatelly on a page.
I'm generating content in for loop, and part of the content is a graph, which is generated based on the current state. Idea is to have a component that calls the method that generates the graph and persists the result(with expire time), gives it an unique id an generates <img with the link to the service that retreives the result in subsequent request later on from storage. This approach has issues, but brings a more natural feeling while generating a page, another problem is that it can be misleeading for those beginners who have trouble understanding why onclick can not call something from server(aside AJAX and alike). further on, this approach if usefull can then be broadened to use serializable objects instead of real data(data would be generated when needed), reduce the storage cost, and make it possible to be used in an situation where the result is not shown immediatelly like an graph, but later when clicked like an pdf document. Davor Hrg On 8/29/05, Vjeran Marcinko <[EMAIL PROTECTED]> wrote: > > ----- Original Message ----- > From: "Kent Tong" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Monday, August 29, 2005 3:13 AM > Subject: Re: The hardest problem ever > > > > Vjeran Marcinko <vjeran.marcinko <at> > > email.t-com.hr<http://email.t-com.hr>> > writes: > > > >> It's all nice and easy, but problem is that my page that implements > this > >> interface (provides PdfDocument), is dependant upon some parameter that > >> was > >> paseed to it for rendering, but PDF generation is subsequent request > and > >> page doesn't have this parameter anymore. > > > > Your PdfLink component should take a parameter and pass it to > > your service, which will in turn pass to the PdfHandler. This > > will work even in a loop. > > Meaning, anyone who is making such general purpose service/component > should > take care to provide way to pass arbitrary number of parameters (such as > DirectLink offers) in some XServiceLink, and offer IRequestCycle argument > inside XServiceProvider interface, so one could fetch parameters by > cycle.getListenerParameters() in it because providing can be dependant > upon > various app-specific parameters ? > > And, "client" persisted property that would get set during each loop turn, > thus generating additional URL parameter to all DirectLinks inside loop > would not function ? Because there's no detailed docs about For component, > and about various client peristence strategies, I guess MindBridge would > know this best. > > -Vjeran > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
