Note that there are some explanatory texts on larger screens.

plurals
  1. POUsing Meetup Stream in PHP to import new events
    primarykey
    data
    text
    <p>The meetup API allows you to get pushed data updates. A <code>CURL</code> request that looks as followed:</p> <pre><code>http://stream.meetup.com/2/open_events </code></pre> <p>Will return a constant stream of updated events. This imported stream just keeps updating as new data is pushed to it. I am trying to think up the best way to work with this stream, and I am not sure what is standard. I was thinking to just run a <code>CURL</code> request within a while loop but that would just run forever and running that from a controller function in my codeigniter project seems impractical. What is the proper way to interface with a seemingly infinite stream of events like this? Is there a better way than running a process from a controller function? Would it be more sensible to run a chron-job that woke up every so often to continue processing from where it left off before? </p> <p>UPDATE: Further investigation has shown me that importing data from this stream uses chunked-transfer encoding. What is confusing to me is that this stream seems to be infinite. It just keeps outputting data non-stop. I still do not understand how to import data from a stream of data like this. A cron job also does not seem to be the answer for importing a stream like this into my mysql database.</p> <p>This is a link to the resource that documents the Meetup Stream: <a href="http://www.meetup.com/meetup_api/docs/stream/2/open_events/" rel="nofollow">http://www.meetup.com/meetup_api/docs/stream/2/open_events/</a></p> <p>Thank you for the help.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload