|
From: Marty K. <mrk...@co...> - 2013-11-20 19:29:40
|
On 11/20/2013 11:04 AM, Ralph Lange wrote: > If I remember correctly, > > we decided to bite the bullet and rename/refactor our modules to replace > the term "channel" with "pv", so that pvAccess connects to pvs, and the > pvAccess server implements a PvProvider to give pvAccess an interface to > pvData structures, etc. > > I still see a lot of "Channel" inside pvAccess. Let me propose a less disruptive change. I think the only name that V4 should not use is channel access. Thus the name channel is OK. http://www.thefreedictionary.com/channel Has the definition: 1. The bed of a stream or river. ... 6. A course or pathway through which information is transmitted: new channels of thought; a reliable channel of information. 7. A route of communication or access. Often used in the plural: took her request through official channels. ... Both channel access and pvAccess satisfy 6) or 7). If this is accepted the only name in pvAccess that needs to change is ChannelAccess. In Java this is an interface. In C++ it is a class. In addition the documentation (many places) must be checked to see that channel access is only used to talk about what comes with epics base. We could rename ChannelAccess with minimal change to code and Documentation. Changing the name Channel affects LOTS and LOTS of code and documentation. I also suggest that the name ChannelAccess be replaced by PVAccess. Marty > The more code we produce that uses the old names, the more hazzle it > will be to change them. > > What is the planned time scale for the transition? > > Thanks, > ~Ralph > > > ------------------------------------------------------------------------------ > Shape the Mobile Experience: Free Subscription > Software experts and developers: Be at the forefront of tech innovation. > Intel(R) Software Adrenaline delivers strategic insight and game-changing > conversations that shape the rapidly evolving mobile landscape. Sign up now. > http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk > |