> 
> What, exactly, do you mean?
> Transparent upgrades are a serious challenge for all software, not just
> SlimServer. The more you expect it to remember, the harder it gets. At
> some point, it becomes impractical.
> 
> Seems to me that a reasonable list of things for the SlimServer to
> remember across upgrades (IMHO) are
> 1) remember your library directory
> 2) remember your player names
> 3) remember choses skin
> 
> I personally don't care about plugins, some others may care more. At
> some point, it may be too hard.
> 

I mean to upgrade without leaving stuff behind that causes it to crash.
There are currently no shortage of active threads talking about how the
6.3 plugins, and the default2 skin that get left in place during upgrade
are causing issues.  By and large, when I upgrade software it works, and
is not hampered by the fact that an earlier version had been installed.

> 
> Its the server for a SlimDevice, the SqueezeBox.
> I don't see any reason to worry about it, an old obsolte PC runs it
> perfectly. Mine has been up
> 13:30:13 up 460 days, 41 min, 2 users, load average: 0.07, 0.13, 0.09
> 

I run it on a dedicated box with an 800mhz processor, win2k3 and 512MB
RAM.  When the scanner is running, navigating the web interface is
painful, and my SB's interface gets laggy.  I'm not at home right now,
so I can't quote any numbers, but I do remember being rather astonished
at the size of the memory footprint of both the scanner and slim.exe
itself.

They also want this to run on NAS devices, which are pretty limited on
proc. and memory resources...

> 
> I probably have to add AJAX on the interface to what I do for a living,
> and I am terrified. Doing it properly for lots of OS and browser
> combinations looks extremely hard. Just testing all the combinations is
> going to take many weeks if not many months.
> 
> AJAX is cool, but the tools to support it professionally are seriously
> lacking. IMHO, YMMV, etc.
> 

No, it's not that hard.  I'm a programmer as well (8 years in the biz),
and have been doing AJAX for about a year or so.  Compatibility is not
an issue, there's just MS vs. EVERYONE ELSE on exactly how you call up
the XMLHttpRequest object, but it's pretty easy to pick the right way
via object detection ... or just use one of the many and useful AJAX
libraries out there.  I think I remember seeing that Fishbone uses
Prototype.js ... but I could be mistaken.

As for debugging tools, pretty much using the FireBug extension in
Firefox is all I've ever needed, and then standard debugging techniques
from there.  It's not as hard as you think, but you have to stop
thinking the way you used to in regards to how web-apps are supposed to
work.

Now, you're going to say, "if your such a fantabluous programmer why
don't you contribute to the project."  

Fair jab.  I have two reasons:
1. I typically do a 50 hour week at the office.  I also have a wife and
child ... and I do a little freelance work too.  By the time I finish
programming for money, I just want to Listen to my SB, talk to my wife
and play with my baby.  As much as I'd like to contribute, I frankly
don't have the time.

2. Perl. I hate it.  Makes my head hurt.


-- 
jeffluckett
------------------------------------------------------------------------
jeffluckett's Profile: http://forums.slimdevices.com/member.php?userid=6179
View this thread: http://forums.slimdevices.com/showthread.php?t=26874

_______________________________________________
discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss

Reply via email to