André van Toly added a comment -
2011-08-25 17:58 There are three mechanisms involved here when new media is created in OIP. Most importantly when media is uploaded it is not immediately (but almost) indexed by the search engine Lucene. Besides that there is an caching mechanism in effect on the homepage that caches items for about 120 seconds.
1. Media is almost immediately visible on a users media or profile page since these derive from a MySQL query on the database.
2. The /media page gets its content from Lucene, so it may take a (short) minute before its visible here. Indexing a new media item is done almost immediately after is becomes available (= upload completely finished). Lucene gets a signal from MMBase and does its work.
3. The homepage gets its 'New media' content from Lucene. Besides that it caches the 'New media' list for 120 seconds. This is a bit of a legacy thing. Before the automatic previews of videos were created, we uploaded images ourselves and it looked a bit silly to have the default grey image on our homepage. Besides the cache lessens the number of queries on Lucene (although that's not really an issue since Lucene can handle quite a lot).
If you feel we need to change this, we can, but I see no real reason and propose just to close this issue with 'Won't fix'.
Bug
Closed
Major
1. Media is almost immediately visible on a users media or profile page since these derive from a MySQL query on the database.
2. The /media page gets its content from Lucene, so it may take a (short) minute before its visible here. Indexing a new media item is done almost immediately after is becomes available (= upload completely finished). Lucene gets a signal from MMBase and does its work.
3. The homepage gets its 'New media' content from Lucene. Besides that it caches the 'New media' list for 120 seconds. This is a bit of a legacy thing. Before the automatic previews of videos were created, we uploaded images ourselves and it looked a bit silly to have the default grey image on our homepage. Besides the cache lessens the number of queries on Lucene (although that's not really an issue since Lucene can handle quite a lot).
If you feel we need to change this, we can, but I see no real reason and propose just to close this issue with 'Won't fix'.