Yeap, and im added the multifetch for preloading (singned and not signed)
and for gadgets/metadata


On Fri, Sep 19, 2008 at 8:22 AM, Chris Chabot (JIRA) <[EMAIL PROTECTED]>wrote:

>
>    [
> https://issues.apache.org/jira/browse/SHINDIG-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632636#action_12632636]
>
> Chris Chabot commented on SHINDIG-542:
> --------------------------------------
>
> Adding what Bruno mailed to the list for prosperity's sake:
>
> " 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."
>
> So multi-language-pack fetching is what brought this high on our todo list,
> but content rewriting + concat'ing and other such situations (templating in
> 0.9?) will be a lot more efficient with this in place.
>
> Ps, thanks for picking this up bruno!
>
> > 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

Reply via email to