NetTalk Central

Author Topic: Keep-alive  (Read 3693 times)

Nick

  • Full Member
  • ***
  • Posts: 118
    • View Profile
    • Email
Keep-alive
« on: April 23, 2015, 02:48:54 PM »
How does the keep-alive work?
If I uncheck the setting for it I still see "keep alive" in the headings...
In the past I had to use:

p_web._OkSent = 1
p_web.noopchar = ' '
p_web.NoOp()

to prevent a browse from timing out if searching took too long.

Is that still necessary or does the keep alive the same?

TIA,
Nick

Bruce

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 11250
    • View Profile
Re: Keep-alive
« Reply #1 on: April 24, 2015, 05:39:07 AM »
Keep-alive has nothing to do with that.

Nick

  • Full Member
  • ***
  • Posts: 118
    • View Profile
    • Email
Re: Keep-alive
« Reply #2 on: April 24, 2015, 05:46:15 AM »
So this is still valid?
p_web._OkSent = 1
p_web.noopchar = ' '
p_web.NoOp()

Bruce

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 11250
    • View Profile
Re: Keep-alive
« Reply #3 on: April 24, 2015, 06:41:14 AM »
well, I guess if your browse search takes more than 30 seconds then I'd be looking to add keys, or whatever to make the search a lot faster. I'm not sure folks will happily wait > 30 seconds for a set of search results these days.

But I guess if that code worked before it might work now. I'm not sure your NoOpChar should be empty - I think maybe it should be a '.', but this part of things has not changed... (Although sending noOps in a browse context could probably break the xml I guess. It was only designed for reports, not browses.

cheers
Bruce

Nick

  • Full Member
  • ***
  • Posts: 118
    • View Profile
    • Email
Re: Keep-alive
« Reply #4 on: April 24, 2015, 07:37:23 AM »
You're right. I put that in about 5-6 years ago.
I better can skip it I guess. See if someone complains...

Cheers,
Nick