RE: Queue Order Changing

From: Dylan Douglas <dylan_at_mediadefender.com>
Date: Fri, 6 Apr 2007 12:41:57 -0700

Z-

Been working on this since yesterday. I think "add" and "delete" should
probably be part of status, since hash would already be telling me what
hash would be added or deleted. Having them as separate variables would
just confuse things.

>1. account=<string>
>2. hash=<string>
>3. after=<string> - hash that the above hash is now after, or not set
if moved to the top of the queue
>4. status=<lock|unlock|add|delete|move>

If 3 is optional for status:add and status:move. 3 won't be included
for status:lock, status:unlock, or status:delete.

If I remember right, the top 50 will be shown to the user and those are
the ones that they can play with. So, if they found something they
wanted to download, it would get added to the top of the queue. If they
then wanted to move it down to queue position 25, that's their own
doing. But, it wouldn't have any priority other than the queue
position.

-D

>-----Original Message-----
>From: Stefan Kaczmarek [mailto:stefan_at_thezonie.org]
>Sent: Tuesday, April 03, 2007 6:11 PM
>To: Dylan Douglas
>Cc: Ivan Kwok; Ben Ebert; Ty Heath; Jay Mairs
>Subject: Re: Queue Order Changing
>
>Ok, as per our super-cool chat, I've implemented the order changing
>stuff, so I guess we can have a edit_queue.php (or modify_queue.php
>or alter_queue.php or just queue.php if you want all the code in one
>file) that accepts the following variables:
>
>1. account=<string>
>2. hash=<string>
>3. after=<string> - hash that the above hash is now after, or not set
>if moved to the top of the queue
>4. delete=<string> - hash to delete from the queue
>5. add=<string> - hash to add to the queue (are we going to allow
>adds to the queue beyond the high priority downloads? Will those be
>added to the queue, or kept separate? If they are added to the queue,
>then the priority of each item should be stored and sent down as well)
>6. status=<lock/unlock> - or we can just have "lock" and "unlock" be
>things I just set, you know like "tivo.php?hash=123...def&lock"
>
>Let me know if you want to change this stuff, or if you want to break
>it up into separate files.
>
>- Z
>
>On Apr 3, 2007, at 4:04 PM, Dylan Douglas wrote:
>
>> Z-
>>
>> Yeah, once you tell me that hash X should be at position N, all the
>> intermediate items between N_t0 and N_t1 will also change.
>>
>> E.g.: You have 10 through 17. The user moves 16 to 12.
>The existing
>> 12 through 15 are shifted up one to become 13 through 16.
>>
>> That's why I'm thinking of only dealing with a hash and position to
>> prevent moving the wrong hash to the right position. You
>just have to
>> deal with the first request (move this hash there) and then the web
>> service will take care of moving all the other stuff.
>>
>> -D
>>
>>
>>> -----Original Message-----
>>> From: Stefan Kaczmarek [mailto:stefan_at_thezonie.org]
>>> Sent: Tuesday, April 03, 2007 1:14 PM
>>> To: Ivan Kwok; Ben Ebert; Ty Heath; Jay Mairs; Dylan Douglas
>>> Subject: Queue Order Changing
>>>
>>> D,
>>>
>>> So I'm working on the queue order stuff, and you said that
>you wanted
>>> to reference changes by the position in the db, not the webpage.
>>>
>>> So okay, what I have is a collection of objects in a
>series, numbered
>>> 0-n (the web page index) and each contain a db position that I get
>>> from the server.
>>>
>>> Now, when a user changes an item's position, I check the web order,
>>> and from there I can figure out which item moved from where, and I
>>> can tell you that "db pos item N moved to replace db pos item M" ...
>>> But I don't know how you're storing stuff in the db, so
>does that now
>>> update the item position values? So, does pos item N now change its
>>> position value to M? And do all of the items in between shift their
>>> position values as well?
>>>
>>> The collection maintains the original position values (the web, 0-n
>>> numbers) so I can track an item's movement during multiple
>orderings.
>>> (Until they refresh the page, of course.) I just don't know if your
>>> db position values are fixed or what.
>>>
>>> - Z
>>>
>
>
Received on Fri Sep 14 2007 - 10:56:01 BST

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