![]() ![]() The problem with keeping them in memory is that if you have a timeout or hit the memory limit, all that data is gone and you need to start from scratch (assuming you can still access the data). The most obvious use case for the Queue API is in aggregating data ( feeds), where you have a huge batch of items that need to be turned into Drupal content.īefore the Queue API, you could either keep this list of items in memory, or you could write them to a cache. ![]() In Drupal terms, these tasks would be data processing - you have some data that needs to be used to do something else. If you have a hundred things to do in a day, you need to write them down and cross them off the list as you do them. It's very similar to the way we make to-do lists for household chores. The Queue API is designed to manage tasks. One of the additions to Drupal 7 that went in without a lot of fanfare was the Queue API.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |