Postponed
Project:
HTTP Parallel Request & Threading Library
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
26 Oct 2012 at 18:57 UTC
Updated:
16 Nov 2012 at 23:12 UTC
Comments
Comment #1
mikeytown2 commentedSadly this is expected for the 1.x branch. You can add an anchor (
#) to the URL to separate them out though, so not all is lost. Things could change in the 2.x branch. Open to ideas on how you would like it to work.Example below. The $data array will contain 4 different URLs.
Comment #2
obrienmd commentedRight - I used a random query parameter for now to work around it. Honestly, in 2.x, I think it makes sense to just have a numerically-keyed array of responses with the url being included in each one somewhere?
Comment #3
mikeytown2 commentedIssue is I like the ability to access the URLs info via key; the key being the URL.
Comment #4
obrienmd commentedYeah, I can see why you would in many use cases. Hrm... I suppose I don't really have an issue with mocking up a query param or anchor :) I'll ruminate a bit more...
Comment #5
obrienmd commentedThought about it a bit more... I suppose you could return an array that looked like this (example is 2 requests to Google and 1 to Yahoo):
Comment #6
mikeytown2 commentedGoing to postpone this issue. In the future we can do an array of arrays but this would be an API breaking change thus it would have to go in a new version.
Comment #7
obrienmd commentedCool, thanks!
Comment #8
mikeytown2 commented