Search Feedback

27
votes

Put the networking HLAPI into its own separate namespace, separate from the Transport layer

Networking

-

-

Building a custom networking system on top of the transport layer is currently very troublesome due to class names often conflicting with the HLAPI classes.

Would it be possible to put the entire HLAPI into its own namespace?
( for example UnityEngine.Networking.HLAPI )

Comments (1)

  1. C2778d4182b1b39798b1e8e74dd2e143?d=mm

    Fydar

    Aug 24, 2017 11:24

    I agree with this, this might happen when Unity creates the Networking Library separate to the UnityEngine libraries for use outside of Unity.

Your opinion counts

Help us make things better. Share your great idea for improving Unity or vote for other people’s.

Log in to post a new idea

Categories

All

(9911)

2D

(260)

Ads

(50)

AI & Navigation

(77)

Analytics

(115)

Animation

(366)

Asset Store

(271)

Assets

(510)

Audio

(169)

Cloud Build

(122)

Collaborate

(45)

Docs & Tutorials

(217)

Editor

(2293)

Everyplay

(13)

Game Performance Reporting

(16)

General

(890)

Graphics

(821)

GUI

(397)

Input

(157)

Licensing

(84)

Networking

(176)

Physics

(362)

Platforms

(427)

Profiling & Optimization

(76)

Runtime

(171)

Scripting

(1097)

Terrain

(164)

WebGL

(138)