You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by "impetus technologies (JIRA)" <ji...@apache.org> on 2008/09/16 15:20:44 UTC
[jira] Commented: (SHINDIG-542) curl_multi fetcher
[ https://issues.apache.org/jira/browse/SHINDIG-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631390#action_12631390 ]
impetus technologies commented on SHINDIG-542:
----------------------------------------------
Hi Chris,
I was trying to map the curl_multi usages in the PHP-shindig server.
As of now I got only a single curl reference in BasicRemoteContentFetcher.php. As per the current behavior, Shindig uses this class to get the gadget content and may be in some OAuth requests. If this is correct, in what cases can we have multiple requests in Shindig, for which curl_multi will be actually useful?
Can I have some scenarios which can prove the advantage this implementation?
> 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.