AirVision Node-Node Transfer - History Page

	Date/Time	Made By	Edit Note	Type	Scope
	Feb 24 2011, 2:49 PM EST	sdrevik		edit	6 words added 421 words deleted
Change: Communications should begin with a ‘handshake’ using a shared key between the Central and the side node, unique to each site. The listener should not respond to requests if the keys don’t match.(simple hashed text string, like our password storage?)Also verify DBS schema versions? Goal AirVision View changes from previous version. (Word count: 7)
	Feb 24 2011, 2:48 PM EST	sdrevik		undelete	No content added or deleted.
Change: Restored by sdrevik Feb 24 2011, 2:48 PM EST for: no reason given
	Jan 20 2011, 5:34 PM EST	sdrevik	no longer needed	delete	No content added or deleted.
Change: Deleted by sdrevik Jan 20 2011, 5:34 PM EST for: no longer needed
	Nov 3 2010, 9:59 PM EDT	sdrevik		edit	12 words added 11 words deleted
Change: another node for certain data types,a andsite toPC synchronizerunning configurations.AV-Trend.Typical User AirVision administrator would set up polling as an automatic functionAirVision administrator would manually “download” or “upload” configurations from site node. The site node would not need to start an upload by itself. View changes from previous version. (Word count: 430)
	Jul 6 2010, 4:48 PM EDT	sdrevik		edit	42 words added 169 words deleted
Change: Both Central and the AV-Trend / Site Node system would be required to be running SQL Server 2008 (SQL 2005 not supported for this function) Current Digi-Trend Function Minute data files are stored in a file with name coded to Site ID, Julian Day, and Year.File is View changes from previous version. (Word count: 428)
	Oct 11 2009, 12:50 PM EDT	sdrevik	Moved from: Communications	move	No content added or deleted.
Change: Moved by sdrevik Oct 11 2009, 12:50 PM EDT
	Oct 4 2009, 6:08 PM EDT	sdrevik		edit	529 words added 43 words deleted
Change: the Central and the side node, unique to each site. The listener should not respond to requests if the keys don’t match.(simple hashed text string, like our password storage?)Also verify DBS schema .versions? Goal AirVision Functions – Configuration Management Allow for the user to manual "Polling"send View changes from previous version. (Word count: 548)
	Dec 3 2008, 9:42 PM EST	sdrevik		edit	19 words added
Change: for AirVision nodes to transfer data between nodes . "Polling" of a node by another AirVision node (or the Central node) would be protected with an authentication system.Must include complete subset of database record, annotations, flags, calibration records, ??? View changes from previous version. (Word count: 62)
	Mar 23 2008, 8:57 PM EDT	sdrevik		edit	44 words added
Change: Utilizes an ability to automate an XML export of data and XML import of data FTP’d in (or web service to accept transfer) for AirVision nodes to transfer data between nodes . Must include complete subset of database record, annotations, flags, calibration records, ??? View changes from previous version. (Word count: 43)
	Mar 23 2008, 8:40 PM EDT	sdrevik		create	No content added or deleted.
Change: Created by sdrevik Mar 23 2008, 8:40 PM EDT for: no reason given