Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
I
iotivity-classic
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3,289
    • Issues 3,289
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • 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
  • IoTivity
  • iotivity-classic
  • Issues
  • #95

Closed
Open
Opened Dec 08, 2014 by Rami Alshafi@ramiOwner

Add timeout to default entity handler for collection batch interface

A GET/PUT request on the batch interface of a collection resource using the default entity handler will result in each contained local resource's entity handler being invoked. When the stack receives each of the contained resources' responses, it will combine the responses and send the aggregate response to the client.
If one or more local resource entity handlers do not respond, no aggregate response is sent to the client. A timeout needs to be added so that if a response is not received within a defined time, then the default entity handler for the batch interface of a collection resource will generate an appropriate timeout message for the local resources that did not respond, and then send the aggregate response that includes the timeout error messages.
Consider various ways to set the timeout value:

  • defined per platform (hard-coded in config file)
  • set as parameter in the makefile
  • via a new API
  • other?

JIRA migration meta data

  • JIRA Issue ID: IOT-108
  • Reporter: dhudson
  • Assignee: dhudson
  • Creator: dhudson
  • Created at: 2014-12-08T13:13:11.000-0800
  • Found in Version: e61ce0f3
  • Fix in Version: None
  • Issue Severity: Normal
  • Reproducibility: Always (100%)
  • Operating System: Ubuntu
  • Hardware/ OEM Platform: None
  • External URL: None
  • Bugzilla ID: None
  • Product: None
  • Status: Closed
  • Components: SDK
  • Priority: P2
  • Due Date: None
  • Issue Type: New Feature
    END of JIRA migration meta data

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: iotivity/iotivity-classic#95