Experimental Physics and
Industrial Control System

Am 19.11.18 um 17:56 schrieb Michael Davidsaver:
>> The CA client library could be extended to handle PV names longer than
>> say 29 bytes by hashing them transparently. So what goes over the
>> network is only the hashed name, but the programs that /use/ the CA
>> client library need not know or care.
> 
> I'm a bit perplexed that overcoming an implementation limit of name
> length should involve what sounds like effectively a protocol change.

No, not at all. No protocol change is involved.

> In that it would prevent old and new clients/server from interoperating.
> Am I missing something?

Yes: the hashes are encoded in ASCI so they remain valid PV names. The
proposal is fully compatible. In fact, the protocol remains exactly as
it is now. Changes involve only the client library and a bit of IOC code
for convenience.

Cheers
Ben

Attachment: signature.asc
Description: OpenPGP digital signature

References:

EPICS V3 PV name length limits and how to get around them Benjamin Franksen via Core-talk

Re: EPICS V3 PV name length limits and how to get around them Michael Davidsaver via Core-talk

Navigate by Date:

Prev: Re: EPICS V3 PV name length limits and how to get around them Benjamin Franksen via Core-talk

Next: Re: EPICS V3 PV name length limits and how to get around them Ralph Lange via Core-talk

Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <2018>  2019  2020  2021  2022  2023  2024 

Navigate by Thread:

Prev: Re: EPICS V3 PV name length limits and how to get around them Benjamin Franksen via Core-talk

Next: Build failed in Jenkins: EPICS-7 #165 Jenkins EPICS PSI via Core-talk

Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <2018>  2019  2020  2021  2022  2023  2024