Dumb Piced

Discussion in 'C-Touch/HomeGate/SchedulePlus/PICED Software' started by Dave Byron, Apr 30, 2009.

  1. Dave Byron

    Dave Byron

    Joined:
    Aug 3, 2004
    Messages:
    835
    Likes Received:
    0
    Location:
    Casurina
    See even in version 4.6 Piced is still dumb in that it not knows when C-Gate is starting and waits - instead it still outputs an error message.

    Come on Darren fix it.

    dave
     
    Dave Byron, Apr 30, 2009
    #1
  2. Dave Byron

    Darren Senior Member

    Joined:
    Jul 29, 2004
    Messages:
    2,361
    Likes Received:
    0
    Location:
    Adelaide, South Australia
    I could have sworn I fixed that. Are you using a really slow computer?
     
    Darren, May 1, 2009
    #2
  3. Dave Byron

    Memphix

    Joined:
    Aug 31, 2006
    Messages:
    248
    Likes Received:
    1
    Location:
    Australia
    I use to have that problem. Appears fixed here.
     
    Memphix, May 1, 2009
    #3
  4. Dave Byron

    [IL]NewGen

    Joined:
    Aug 3, 2004
    Messages:
    121
    Likes Received:
    0
    Location:
    Melb, Australia
    yeah, it truely fails on a P3 or an original Celeron, PC speed is a factor:p
     
    [IL]NewGen, May 22, 2009
    #4
  5. Dave Byron

    ashleigh Moderator

    Joined:
    Aug 4, 2004
    Messages:
    2,398
    Likes Received:
    26
    Location:
    Adelaide, South Australia
    PC speed is a factor. Here is why:

    PICED has to start cgate.

    Cgate takes a certain amount of time to start, and the slower the PC the longer (elapsed) time this is.

    NOW...

    PICED could do one of 2 things after starting cgate:

    1. Wait for it forever.
    2. Wait for a while (a timeout) and if it does not start, then barf and raise an error message.

    You can see where this is going:

    Option 1: Works fine on slow PC's BUT if cgate can't or wont start for some reason, the program stops responding, there is no notification to the user, and there are complains that "PICED has locked up". Blah blah blah.

    Option 2: Works fine on moderate to fast PC's. Leads to false reporting on stone age PCs (could make the timeout longer to get around this.... BUT.... there are limits to how long you should wait. The trouble with really long timeouts is that it LOOK the same as option 1.) And if cgate can't or won't start for some reason, at least you do get an error report.

    So the trouble is, both options have a sucky side-effect, neither is a perfect solution. On balance, option 2 is better than option 1. Which then just leaves tweaking the timeout. And as above - the longer the timeout, the less use it is.

    Older PCs, and PC's using especially slow anti-virus software make for a great deal of variability, for which there is no right solution.
     
    ashleigh, May 23, 2009
    #5
  6. Dave Byron

    Ingo

    Joined:
    Dec 2, 2006
    Messages:
    290
    Likes Received:
    1
    Location:
    South Africa
    I am no expert but what about a combination of both. Have C-Gate 'signal' that it is ready so that any application that depends on it loads immediately thereafter. The second change is to put a user configurable timeout in whatever application relies on c-gate with a default value that is acceptable for most PC's. If the user has one that was used on Noah's Ark then he can set the timeout larger otherwise the c-gate signal will initiate an application load way before the timeout is reached.

    The timeout value could also be a commandline parameter.

    My 2c worth...
     
    Last edited by a moderator: May 23, 2009
    Ingo, May 23, 2009
    #6
  7. Dave Byron

    ado_civon

    Joined:
    May 24, 2009
    Messages:
    27
    Likes Received:
    0
    Location:
    Brisbane
    a P3........... my 2c worth :)
     
    ado_civon, Jun 9, 2009
    #7
Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.