Re: [Edgex-tsc-core] Delhi -- Cleaner Separation of Internal/External Packages
Dell Customer Communication
To continue the thread, I wanted to give visibility to Issue #368. I’ve submitted the first PR against that issue to address the items below and after doing some work, my thinking has shifted a touch. Please see below:
I'm about to submit the first PR for this issue in which the majority of the delineated code has been moved to its new location. I'm adding this comment to record my thoughts at this point on what the end goal is going to look like. There will be a couple more subsequent PRs I think.
We had previously discussed keeping the edgex-go/core directory as the location of externally usable code but I’m thinking an edgex-go/external directory makes more sense, as described above. The term “core” has a specific meaning within EdgeX, referring to a specific tier within the platform.
The following directories will ultimately go away:
Their respective clients would go into the edgex-go/external/clients package and their implementation logic would go into
In particular I want to see if there is any objection to the external package and proposed grouping.
Work done so far is here PR #369
Senior Principal Software Engineer
Dell Technologies | IoT DellTech
Round Rock, TX USA
From: Steve Osselton [mailto:steve@...]
Sent: Monday, July 2, 2018 7:39 AM
To: Conn, Trevor
Cc: EdgeX-GoLang@...; edgex-tsc-core@...
Subject: Re: [Edgex-tsc-core] Delhi -- Cleaner Separation of Internal/External Packages
This all looks pretty sensible to me.
On 30 June 2018 at 02:41, <Trevor.Conn@...> wrote:
IOTech Systems Ltd.