Project

General

Profile

Actions

Feature #3160

closed

Permit scope=local in WebSocketTransport

Added by Alex Afanasyev over 9 years ago. Updated about 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Faces
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
3.00 h

Description

Currently, all WebSocketFaces are considered non-local for ScopeControl purposes.

A WebSocket connection to a local NFD instance using a loopback address should be considered local, so that an application can have access to /localhost namespace including NFD Management.


Related issues 1 (0 open1 closed)

Blocked by NFD - Feature #3169: WebSocketTransportClosedYukai Tu

Actions
Actions #1

Updated by Alex Afanasyev over 9 years ago

  • Blocked by Task #3088: Refactor Face as LinkService+Transport added
Actions #2

Updated by Junxiao Shi over 9 years ago

  • Subject changed from Make WebSocketFace connected through localhost "local" to Permit scope=local in WebSocketTransport
  • Description updated (diff)
  • Estimated time set to 3.00 h

In fact, ScopeControl rev1 says:

Generally, the following faces are local:
WebSocket face whose remote address is a loopback address

But this is never implemented.


I notice ScopeControl refers to Interest Scope field which has been removed.
I have updated that page to rev2 which does not refer to the Scope field.

Actions #3

Updated by Junxiao Shi over 9 years ago

  • Blocked by deleted (Task #3088: Refactor Face as LinkService+Transport)
Actions #4

Updated by Junxiao Shi over 9 years ago

Actions #5

Updated by Junxiao Shi about 9 years ago

  • Status changed from New to Closed
  • Assignee set to Yukai Tu
  • % Done changed from 0 to 100

This is completed together with #3169.

Actions

Also available in: Atom PDF