RE: Queue.php / Push.php

From: Dylan Douglas <>
Date: Fri, 30 Mar 2007 08:34:39 -0700

Sorry, metainfo.php


        From: Stefan Kaczmarek []
        Sent: Thursday, March 29, 2007 12:52 PM
        To: Dylan Douglas
        Cc: Ben Ebert; Ivan Kwok; Jay Mairs; Ty Heath
        Subject: Re: Queue.php / Push.php
        Is the metadata.php file there? gives me a 404.

        - Z

        On Mar 28, 2007, at 1:14 AM, Dylan Douglas wrote:

                I've stubbed the metadata.php script. It queries the
database, so call it using "e8c8446ae2c09a85eeb44dcf8aad2239e43c813d".
The vars are hash and callback. The return for this hash and callback
"sexytime" is:
                sexytime( { "hash":
"e8c8446ae2c09a85eeb44dcf8aad2239e43c813d", "title": "Sexytime Bikini
Beach.avi", "size": "122649320", "codec": "dv50", "length": "4871",
"views": "29710", "tags": [ { "tag": "b00bies" }, { "tag": "flashing" },
{ "tag": "ggw" }, { "tag": "naughty" }, { "tag": "porn" } ] } )
                I can add others, but thought this would be good enough
to start with.
                Ps. the hash also has a thumbnail associated with it.
                Dylan Douglas


                From: Stefan Kaczmarek []
                Sent: Tue 3/27/2007 2:56 PM
                To: Dylan Douglas
                Cc: Ben Ebert; Ivan Kwok; Jay Mairs; Ty Heath
                Subject: Re: Queue.php / Push.php

                Okay, so I've updated the files at
                It is assuming that TheZonie is logged in, and it is
getting the
                Recent Download and Queue data from the server. (It is
also getting
                the Library stuff if you have the application running,
which none of
                you will at this point.)
                It would be cool if some of the recently downloaded and
queue hashes
                could have valid thumbnails associated with them. ;)
                I see that the queue data is "hash", "position", and
"status". I
                thought we wouldn't need the "status" in there, because
                application will be updating what is transferring and
what isn't in
                near-real-time, so the server doesn't need to tell me
what's running
                and what's not.
                In terms of the queue position, I basically get
notification when the
                order has changed, but not what changed where. What I
have is the
                order of the objects, and those objects can have
identifying data
                associated with them. So I can store the order of the
objects, and
                then when it changes, I'll be able to see what the new
order is. I am
                assuming I would then be able to figure out which one
has moved, and
                then tell you which one moved, and to what other
object's position it
                I'm fine with the modify.php ... Although maybe it
should be
                Now, in terms of all the other meta-info about the
hashes ... You
                know, file name, length, size, rating, etc. ... When's
that going to
                be available? And will it come with the hashes as a part
of the queue
                return? Or would I have to do a separate query for each
hash to get
                its meta data? (That would suck balls.)
                - Z
                P.S. (There is some weirdness with the selection of the
queue items,
                which I just noticed, but no big deal.)
                On Mar 27, 2007, at 12:27 PM, Dylan Douglas wrote:
> Z-
> Fixed the queue.php and push.php scripts. Also
created the
> history.php
> script. We probably should figure out a script for
changing: queue
> position/status (downloading/paused)/tivo
> modify.php? I couldn't come up with a better name.
> Anyway, it could be given variables: account=<string>,
> position=<int>, status=<lock|unlock>.
> We should use the position indicators that come from
the database, not
> what is displayed on the webpage. So, at some point
you would
> probably
> say that someone moved something to queue position
10210 or some other
> absurdly high number. I figured that it would be
easier for you to
> keep
> the info on your side, rather than making the database
do the
> calculations.
> When someone moves something from 500 to 486, you
should only send one
> message to the web service. Don't send one for all
the ones that just
> jumped up one position, modify.php will take care of
that part.
> -D
>> -----Original Message-----
>> From: Stefan Kaczmarek []
>> Sent: Monday, March 26, 2007 8:41 PM
>> To: Dylan Douglas
>> Cc: Ben Ebert; Ivan Kwok; Jay Mairs; Ty Heath
>> Subject: Re: Queue.php / Push.php
>> D,
>> When I do this:
>> I get this:
>> sexytime( { "queue": [ ] } )
>> It looks like I have no queue. :(
>> - Z
>> On Mar 26, 2007, at 5:38 PM, Dylan Douglas wrote:
>>> Z-
>>> Updated the queue.php and push.php scripts. They
now are
>> expecting an
>>> account 1 to 128 characters. The only one right now
is "TheZonie",
>>> but
>>> it has a queue of 100 hashes. The queue.php returns
the current
>>> downloads and hashes to download, but not the ones
that have already
>>> downloaded. Maybe we should have a history.php that
>> return only
>>> completed downloads. push.php returns the next hash
that is
>>> waiting to
>>> be downloaded.
>>> All the returns are now in JSON and should be
>> although always
>>> pulling the same info from the database.
>>> -D
>>> -----
>>> Dylan Douglas
>>> MediaDefender
>>> <winmail.dat>
Received on Fri Sep 14 2007 - 10:56:07 BST

This archive was generated by hypermail 2.2.0 : Sun Sep 16 2007 - 22:19:48 BST