Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
I
iTasks-SDK
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 73
    • Issues 73
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 7
    • Merge Requests 7
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • clean-and-itasks
  • iTasks-SDK
  • Issues
  • #14

Closed
Open
Opened Apr 30, 2015 by Jurriën Stutterheim@jstutterheimContributor

Server timeout affecting share refreshes

timeout in Engine.icl affects the rate at which share updates are reflected in the UI.

    timeout iworld = (Just 25, iworld)					//Run 40 times a second, using blocking behaviour

Strangely enough, this will cause share updates to be reflect in 50ms, rather than 25. In general, it takes 2n ms to reflect the share changes.

Two things should happen:

  • Share updates should be disconnected from the TCP timeout in Engine.
  • If a 25 ms timeout is specified, it should take 25 ms to refresh, not 50. This may be solved for shares if they're disconnected from this timeout.
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: clean-and-itasks/iTasks-SDK#14