From: Ralph L. <Ral...@be...> - 2010-06-23 13:55:57
|
Hi Marty, On Wed 23 Jun 2010 7:08:02 Marty Kraimer wrote: > The changes made on branch june2010 have been merged back onto HEAD. > > The following are the main changes: > > pvAccess > > ChannelArray now has a new method setLength which allows a client to set > the length and capacity of an array on the server, Previously a client > could only do this by writing past the current length and/or capacity, > i.e. a client could not force the length or capacity to be smaller. > What was behind the requirement to allow a client (any client?!) to change the array size on the server? I consider this a *very* dangerous feature: Any client can easily crash any IOC by issuing a perfectly legal pvAccess call setting an array to MAX_INT capacity. What is the set-up/situation that would require the client to set the array size? For all arrays I have personally met, the server perfectly knew the size of its data, and there was no reason to allow the client to screw with it. Curious... Ralph |