Also +1 to having more TO clients, and classifying them into language-specific directories. Other suggestions welcome, though.
For instance, longer term, should we target a "Traffic Control" client, with sub-modules for each component? Should the code for these clients live in the language-specific networks (PyPI, CPAN, etc)? On Wed, Jun 14, 2017 at 3:11 PM, Dewayne Richardson <[email protected]> wrote: > +1 (as long as you don't break anything!, lol). I think this will be > valuable because I've already seen 2 different groups out side of ours (at > Comcast) that are reinventing that wheel over and over. We should have > several clients in different languages to open the door to more Traffic Ops > access. > > On Wed, Jun 14, 2017 at 9:35 AM, Scrimo, Robert (Contractor) < > [email protected]> wrote: > > > All, > > > > I would like to add a Python Traffic Ops Client to the > ‘apache/incubator-trafficcontrol’ > > repository but while I am in there I should probably re-organize the > golang > > client that resides in there too. This will most definitely break other > > code dependent on its current location, which is the root of the client > > directory. I am proposing to move the golang code to a newly created > > ‘golang’ directory and add a ‘python’ directory for my Python client. I > > will fix any references to code using the client from within the > > ‘incubator-trafficcontrol’ repository. If anyone has any > > insight/objections/comments about this please respond. I will take your > > silence as approval... > > > > Thank you, > > -Robert > > > > >
