Your preferred object update method : push or pull ?
|
Simil Miles
Creator
Join date: 1 Mar 2007
Posts: 300
|
03-29-2007 16:59
Hello,
Update with the push method : the new version is sent when it is released. Update with the pull method : the new version is sent when you check for it and if it has been released.
Which one do you prefer ?
Notice : this is a question for objects users, not objects creators.
_____________________
UnConWTech @ Flo (144, 84, 224) http://unconwtech.free.fr
SL books http://astore.amazon.com/secondlife-sl-20/
Need a beta tester for quality assurance ? Need a translator for English, French, Spanish ?
|
tristan Eliot
Say What?!
Join date: 30 Oct 2005
Posts: 494
|
03-29-2007 17:00
From: Simil Miles Hello,
Update with the push method : the new version is sent when it is released. Update with the pull method : the new version is sent when you check for it and if it has been released.
Which one do you prefer ?
Notice : this is a question for objects users, not objects creators. I like when the new version is sent when it is released.
|
RobbyRacoon Olmstead
Red warrior is hungry!
Join date: 20 Sep 2006
Posts: 1,821
|
03-29-2007 17:17
From: Simil Miles Hello, Update with the push method : the new version is sent when it is released. Update with the pull method : the new version is sent when you check for it and if it has been released. Which one do you prefer ? Notice : this is a question for objects users, not objects creators. Objects users may not be able to discern the difference. For instance, the products I make are auto-updated, but they are attachments (therefore always worn) that periodically query an update server. If a new update is available, it is sent. The query process is entirely automatic and silent. So, does the end user think an update is sent to them by me or some server who just knows they have the product's older version? Probably. But in fact it is much more like a pull methodology in the technical implementation.
|
Kidd Krasner
Registered User
Join date: 1 Jan 2007
Posts: 1,938
|
03-29-2007 18:07
From: RobbyRacoon Olmstead Objects users may not be able to discern the difference. For instance, the products I make are auto-updated, but they are attachments that query an update server. If a new update is available, it is sent. The query process is entirely automatic and silent. So, does the end user think an update is sent to them? Probably. But in fact it is much more like a pull methodology. Of course they can see the difference. In one they have to push a button to get an update, in the other they don't. The original poster, quite admirably, was looking at it from the user's perspective. You're looking at it from the program's perspective. That's something that many programmers and software engineers do, and there are many times when it's appropriate, but it also shows why so much software can be harder to use than necessary.
|
Warda Kawabata
Amityville Horror
Join date: 4 Nov 2005
Posts: 1,300
|
03-29-2007 18:13
From an end user pov, neither.
The problem with pull is that it ends up filling your inventory with junk, especially if you just can't be bothered to make all teh changes to your inventory that teh update would require, but still want to carry on using teh older version for now. Each time you log in and don't update, you get yet another item to delete.
The problem with push is that you don't know it's been updated.
What I'd like to see is sort of push, but a bit more involved...
When you login/wear an item for the first time in a session, it checks if you are wearing the latest version. if you aren't, it tells you that a newer version is available, and offers to send you the latest version with (yes / remind me later) as options.
ETA: on that update option, (yes / remind me next login / remind me next week / don't remind me again) would be nicer
|
Jopsy Pendragon
Perpetual Outsider
Join date: 15 Jan 2004
Posts: 1,906
|
03-29-2007 18:35
User side? Pull, absolutely. (Unless there is an "Opt-in" option at time of purchase) I prefer not to get updates unless I specifically approve them. Push technology often results in "Opt-out" models. If I buy something and then not use it.. I don't want regular updates for the rest of my life. If I use it often then I may not want new versions if the old version suits my needs fine. Same opinion from a creator side. 
|
Brenda Connolly
Un United Avatar
Join date: 10 Jan 2007
Posts: 25,000
|
03-29-2007 19:04
I prefer the Pull method
_____________________
Don't you ever try to look behind my eyes. You don't want to know what they have seen.
http://brenda-connolly.blogspot.com
|
RobbyRacoon Olmstead
Red warrior is hungry!
Join date: 20 Sep 2006
Posts: 1,821
|
03-29-2007 20:27
From: Kidd Krasner Of course they can see the difference. In one they have to push a button to get an update, in the other they don't. The original poster, quite admirably, was looking at it from the user's perspective. You're looking at it from the program's perspective. That's something that many programmers and software engineers do, and there are many times when it's appropriate, but it also shows why so much software can be harder to use than necessary. Nope, not at all.... There is no button to push in the method I described, and that is my point: A user may not know enough about this process to answer the question that the OP asked in the way that makes most sense.
|
RobbyRacoon Olmstead
Red warrior is hungry!
Join date: 20 Sep 2006
Posts: 1,821
|
03-29-2007 20:43
From: Kidd Krasner Of course they can see the difference. In one they have to push a button to get an update, in the other they don't. Well, that's not at all what I meant in my post, I meant that technically my update method could be considered pull because of the mechanics, but as you can see from my edit there is no button to be pushed or action on the part of a user, so they in fact aren't always aware of the difference. I guess I thought the OP was talking more about technical implementation than an implementation where it was obvious which method was being used. When talking about whether as a user I have to take action to check for updates or not I just don't have a strong preference, though there are reasons why as a developer I prefer a push method for many products.
|
Dnali Anabuki
Still Crazy
Join date: 17 Oct 2006
Posts: 1,633
|
03-29-2007 21:59
As a user, I love auto updates...my stuff checks if its the latest version and then downloads the update..fine by me...
|
Winter Ventura
Eclectic Randomness
Join date: 18 Jul 2006
Posts: 2,579
|
03-29-2007 22:24
I think the best method would be a check on wear/rez, that returns "there is an update available.. would you like to download it?"
_____________________
 ● Inworld Store: http://slurl.eclectic-randomness.com ● Website: http://www.eclectic-randomness.com ● Twitter: @WinterVentura
|
RobbyRacoon Olmstead
Red warrior is hungry!
Join date: 20 Sep 2006
Posts: 1,821
|
03-29-2007 22:39
From: Winter Ventura I think the best method would be a check on wear/rez, that returns "there is an update available.. would you like to download it?" Oh... Nice compromise. I may in fact implement that for some products.
|
Nate Tripp
Stupid and clueless
Join date: 12 May 2006
Posts: 26
|
03-29-2007 22:43
Not that it really matters. The last thing I am thinking when I am purchasing something is how it handles its updates, either way I'll learn to deal with it. Different creators use different methods, the only advantage I really see is often I don't even think to check for any updates, or bother to do so, so I'd go with push.
|