Hi Ropu, Thanks for mentionng this. I had recently started analyzing the issue..and have not gone far!
Looking forward for the fix. Regards, Astha On Tue, Sep 16, 2008 at 7:06 PM, Ropu <[EMAIL PROTECTED]> wrote: > Hi guys, > > i have the multiFetch() already implemented in my sandbox and working with > actual shindig php code base and with the corresponding testCases... > > the idea of it is for some scenarios, such as getting multiple language > pack > (message bundles) with the XML loading + the preloads or for the > gadgets/metadata/ service. > > let me know how you are progressing so we dont code in parallel the same > stuff > > ropu > > On Tue, Sep 16, 2008 at 10:26 AM, Kevin Brown (JIRA) <[EMAIL PROTECTED] > >wrote: > > > > > [ > > > https://issues.apache.org/jira/browse/SHINDIG-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631394#action_12631394 > ] > > > > Kevin Brown commented on SHINDIG-542: > > ------------------------------------- > > > > Right now, the only use for it is when doing preloading, but when the PHP > > code supports rewriting, it is necessary for concatenated files as well. > > > > > curl_multi fetcher > > > ------------------ > > > > > > Key: SHINDIG-542 > > > URL: https://issues.apache.org/jira/browse/SHINDIG-542 > > > Project: Shindig > > > Issue Type: New Feature > > > Components: Gadget Rendering Server (PHP) > > > Reporter: Chris Chabot > > > > > > With the multiple language pack support, there is already a need to > fetch > > several resources at the same time. The current HttpFetcher > implementation > > does a normal (single) curl request per fetch but we could archive a > rather > > large efficiency improvement if we fetched several of them at the same > time. > > > Ideally this would be integrated into the current http fetcher classes, > > so they get the new ability to specify (& return) multiple requests, > instead > > of making a new class for this > > > > -- > > This message is automatically generated by JIRA. > > - > > You can reply to this email to add a comment to the issue online. > > > > > > > -- > .-. --- .--. ..- > R o p u >
