Hi, I'm quite interested in the topic you mentioned (and saved for the next time) - multithreaded generation of content. I was thinking about it few months ago when I wrote portlet that uses soap to connect to some backend information system. When I had one portlet on the page, it was quite ok, but when I put there 5 or so, I noticed few seconds of delay - due to soap calls that takes place one after each other. I think web service portlets (that are 'inherently' slow from my point of view) would benefit a lot from multi-threaded design...
regards, jaro. David Sean Taylor wrote: >>From the SOAP exception, I guess you are using the Stock >>Quote Portlet - this is connecting to a SOAP service over the >>net - perhaps there are delays on that end. > > >>From what I hear that particular web service provider is pretty iffy ;) > > This give me an idea for a new story: > > Timeouts on content generation. > If a portlet doesn't generate its content within n seconds (or ms), then > skip its content generation and move on to the next portlet. The timeout > setting will be configurable in the JR.p. > > > This leads to another story: multi-threaded generation of content. > (Lets save that for next time) > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
