Skip to content
Snippets Groups Projects
Select Git revision
  • dailybuild_linux-x64
  • dailybuild_win32
  • master default protected
  • sqlite
  • rip_abstraction
  • dailybuild_macos-armv8
  • dd_file_lister_filanem_in_desc_color
  • mode7
  • dd_msg_reader_are_you_there_warning_improvement
  • c23-playing
  • syncterm-1.3
  • syncterm-1.2
  • test-build
  • hide_remote_connection_with_telgate
  • 638-can-t-control-c-during-a-file-search
  • add_body_to_pager_email
  • mingw32-build
  • cryptlib-3.4.7
  • ree/mastermind
  • new_user_dat
  • sbbs320d
  • syncterm-1.6
  • syncterm-1.5
  • syncterm-1.4
  • sbbs320b
  • syncterm-1.3
  • syncterm-1.2
  • syncterm-1.2rc6
  • syncterm-1.2rc5
  • push
  • syncterm-1.2rc4
  • syncterm-1.2rc2
  • syncterm-1.2rc1
  • sbbs319b
  • sbbs318b
  • goodbuild_linux-x64_Sep-01-2020
  • goodbuild_win32_Sep-01-2020
  • goodbuild_linux-x64_Aug-31-2020
  • goodbuild_win32_Aug-31-2020
  • goodbuild_win32_Aug-30-2020
40 results

sbbs

  • Clone with SSH
  • Clone with HTTPS
  • Deucе's avatar
    Deucе authored
    wait for a response.  Also, use a single cache list command to check
    the MD5 of both files.
    
    This speeds up startup immensely.  It would be a good idea to do
    something similar in Synchronet any time we send a query and wait
    for a response... as it sits now, we're basically adding extra
    delays that aren't strictly necessary.
    
    Another option would be to *always* flush before a blocking read,
    which would "fix" anything that's not using inkey() with a timeout
    of zero.  This would just generally fix everything I think, unless
    there's something calling inkey() with a very small timeout just
    to avoid 100% CPU or something.
    2f18dc97
    History
    Name Last commit Last update