Brion Vibber wrote: >> yea again if we only issue the big resize operation on initial upload >> with a memory friendly in-place library like vips I think we will be >> oky. Since the user just waited like 10-15 minutes to upload their huge >> image waiting an additional 10-30s at that point for thumbnail and >> "instant gratification" of seeing your image on the upload page ... is >> not such a big deal. >> > > Well, what about the 5 million other users browsing Special:Newimages? > We don't want 50 simultaneous attempts to build that first > über-thumbnail. :) >
Right .. I am just saying the simples path is integrate it into the upload flow. ie The image won't be a known asset until that first uber-thumbnail is generated. Once that happens then its available for inclusion and listed on Newimages. The user won't notice that extra 10-15 second delay because it will be part of the uploading flow. i.e the user is already waiting for their file to be uploaded a few extra seconds of server side processing integrated into that waiting won't be noticed that much and will be easier to integrate with the existing system. (instead of a new concept of "resource is being processed please wait" We do eventually need a "this resource is being processed" concept but I don't know if its good project for the summer of code student to target. --michael _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
