April 2012 Meeting Minutes - Revision history

Jim: modified TLS printing to require an email.ini entry.

2012-06-22T05:53:30Z

modified TLS printing to require an email.ini entry.

← Older revision		Revision as of 05:53, 22 June 2012
Line 87:		Line 87:
	==[[TLS and SSL Support in EmailPtr]]==		==[[TLS and SSL Support in EmailPtr]]==

-	For Comet32 only, this allows email to be sent through providers that require authentication beyond a user name and password. Use of TLS ~~does not require any change to~~ your email.ini file ~~or any special~~ mnemonic.	+	For Comet32 only, this allows email to be sent through providers that require authentication beyond a user name and password. Use of TLS requires a new entry in your email.ini file.
		+
		+	TLS=TRUE
		+
		+	There is no mnemonic for this feature.

	If the response to the EHLO command sent to the server includes the phrase STARTTLS, the email printer will switch the connection to TLS to conclude the authentication process. This is especially useful when using the GMAIL server.		If the response to the EHLO command sent to the server includes the phrase STARTTLS, the email printer will switch the connection to TLS to conclude the authentication process. This is especially useful when using the GMAIL server.

Jim: modified tls printer section

2012-06-01T04:24:04Z

modified tls printer section

← Older revision		Revision as of 04:24, 1 June 2012
Line 85:		Line 85:
	RemoteVsn$ = strip(str(IHexDec(Sub(Sts(0), 19, 2))))		RemoteVsn$ = strip(str(IHexDec(Sub(Sts(0), 19, 2))))

-	==[[TLS Support in EmailPtr]]==	+	==[[TLS and SSL Support in EmailPtr]]==

-	For Comet32 only, this allows email to be sent through providers that require authentication beyond a user name and password. ~~Its use requires only a small~~ change to your email.ini:	+	For Comet32 only, this allows email to be sent through providers that require authentication beyond a user name and password. Use of TLS does not require any change to your email.ini file or any special mnemonic.
-		+
-	~~SecureServer = TRUE~~	+
-	~~ServerAuthenticate = TRUE~~	+
-		+
-	~~There will also be mnemonics to set these parameters. This will be released in Comet32 version .460 and requires REL 12.06~~ or ~~higher~~.	+

		+	If the response to the EHLO command sent to the server includes the phrase STARTTLS, the email printer will switch the connection to TLS to conclude the authentication process. This is especially useful when using the GMAIL server.
		+
	==[[STL Containers for Comet32]]==		==[[STL Containers for Comet32]]==

Barb: /* DocMgr Enhancements */

2012-05-07T18:13:13Z

DocMgr Enhancements

← Older revision		Revision as of 18:13, 7 May 2012
Line 39:		Line 39:
	*Process one or more user-selected documents any way you want, for example, print them, email them, export them,etc (DocProc.ibs)		*Process one or more user-selected documents any way you want, for example, print them, email them, export them,etc (DocProc.ibs)

-	There was interest in having archives that are not necessarily tied to any printer. Furthermore it was requested that a user running DocMgr be able to create one of these as a sub-archive to an existing archive. The sub-archive would ~~not have to~~ be in the ~~same directory as the original~~ archive. DocMgr ~~may have to do~~ a dynamic access if ~~this is~~ the ~~case~~. This feature could be used to further categorize documents from the original archive.	+	There was interest in having archives that are not necessarily tied to any printer. Furthermore it was requested that a user running DocMgr be able to create one of these as a sub-archive to an existing archive. The sub-archive would be in a folder directly under the parent archive. DocMgr will attempt a dynamic access if the user doesn't have access to the sub-folder. This feature could be used to further categorize documents from the original archive.

	Robert noted that the archive record allows for the number of pages and lines in a document but they are always zero. It is not clear whether this info can be provided especially for .pdf documents. We will investigate.		Robert noted that the archive record allows for the number of pages and lines in a document but they are always zero. It is not clear whether this info can be provided especially for .pdf documents. We will investigate.

Barb: /* Wish List */

2012-04-24T19:25:42Z

Wish List

← Older revision		Revision as of 19:25, 24 April 2012
Line 131:		Line 131:

	Jim requested that we have the option to eliminate or at least reduce all the CFAMNetServe log files. Currently a new file is created for each day. Brian suggested they could be off by default with an option to turn them on for debugging. The setting could be stored in the registry.		Jim requested that we have the option to eliminate or at least reduce all the CFAMNetServe log files. Currently a new file is created for each day. Brian suggested they could be off by default with an option to turn them on for debugging. The setting could be stored in the registry.
		+
		+	Greg requested a Comet system level event that would fire under circumstances such as a particular file being updated. He would use this to run a special program in reaction to that update. Robert suggested he might be able to catch file updates by monitoring the Windows event log. Robert also does something like this by having his program write a log file which he then monitors from a background partition. Greg would prefer being able to set this up at the system level so as not to have to modify every program. Jim suggested the file system transaction backup project could possibly have provided a solution. This project is not currently being worked on however.

	==[[Miscellaneous]]==		==[[Miscellaneous]]==

Barb: /* Comet Meeting -- April 17, 2012 */

2012-04-24T18:07:22Z

Comet Meeting -- April 17, 2012

← Older revision		Revision as of 18:07, 24 April 2012
Line 131:		Line 131:

	Jim requested that we have the option to eliminate or at least reduce all the CFAMNetServe log files. Currently a new file is created for each day. Brian suggested they could be off by default with an option to turn them on for debugging. The setting could be stored in the registry.		Jim requested that we have the option to eliminate or at least reduce all the CFAMNetServe log files. Currently a new file is created for each day. Brian suggested they could be off by default with an option to turn them on for debugging. The setting could be stored in the registry.
		+
		+	==[[Miscellaneous]]==
		+
		+	Greg recommended the new power management mnemonics (SetThreadExecutionState) and (GetSystemPowerStatus) [[Mnemonics_"G"#.28GetSystemPowerStatus.29]] be used to prevent a Comet computer from going to sleep as this can cause the network connection to be lost.
		+
		+	It was mentioned that when DHCP is renewed while Comet is running this can cause issues for the security server even if the IP address doesn't change.
		+
		+	A couple of attendees recommended using mySQL to archive Comet data for easy reporting, interfacing with external systems, and web access.
		+
		+	Robert mentioned he had been unable to get the Comet Services working on a Windows 7 machine but couldn't remember the details. He thinks it had to do with errors seeing the USB security token. He moved the token to an XP machine in the network and all is well.
		+
		+	The wiki needs work. Documentation is incomplete. There are broken links, etc. Jim pointed out that it is a wiki and you are all invited to edit. Contact us if don't yet have a user name and password for that.
		+
		+	Jim posed the question of whether requiring one file server license for each file server accessed was a problem. This requirement means that you can consume file server licenses faster than Comet licenses if you need access to more than one server.
		+
		+	Someone asked about using the Comet32 TRACE capability from a CA client. This won't work because the trace window lives on the host.
		+
		+	Jim asked Barb to remind everyone that we had added the ability to access the Windows registry from IB programs - even in Comet16. Your entries may be under either HKEY_CURRENT_USER\Software or HKEY_LOCAL_MACHINE\Software. This is a great
		+	place to store user settings for your application. The new [[Registry_Mnemonics]] are: (RegCreateKey=), (RegSetValue=), (RegGetValue=), (RegDeleteKey=), and (RegDeleteValue=).
		+

	==[[CometConnect and Disaster Recovery]]==		==[[CometConnect and Disaster Recovery]]==

Barb: /* STL Containers for Comet32 */

2012-04-24T17:30:47Z

STL Containers for Comet32

← Older revision		Revision as of 17:30, 24 April 2012
Line 102:		Line 102:
	You can think of a map as a good old fashioned Comet keyed file but in memory instead of on disk. Each entry in a map consists of a key and the data associated with that key. You reference an individual element by its key rather than its element number. Like a vector it grows dynamically as needed. The example of the new [[Replace]] function in the XAP2 discussion above uses a map to perform a merge.		You can think of a map as a good old fashioned Comet keyed file but in memory instead of on disk. Each entry in a map consists of a key and the data associated with that key. You reference an individual element by its key rather than its element number. Like a vector it grows dynamically as needed. The example of the new [[Replace]] function in the XAP2 discussion above uses a map to perform a merge.

-	Each container type has associated functions that are designed specifically for the properties of the container. Some examples are first and last, next and prev for iteration, element counting, and push/pop functions. We would like to expand on these especially the addition of a sorting function. For all the details of our implementation check out the [[STL_Containers]] Reference on the wiki. You can get additional theoretical info by googling "STL Containers".	+	Each container type has associated functions that are designed specifically for the properties of the container. Some examples are first and last, next and prev for iteration, element counting, and push/pop functions. We would like to expand on these especially the addition of a sorting function. It was pointed out that it would be great if the sort function could use the concept of a formatted STR function to define the format of the sorted data via an editmask (see request for this in "Wish List" below).
		+
		+	For all the details of our implementation check out the [[STL_Containers]] Reference on the wiki. You can get additional theoretical info by googling "STL Containers".

	==[[CometPDF]]==		==[[CometPDF]]==

Barb: /* STL Containers for Comet32 */

2012-04-24T17:26:13Z

STL Containers for Comet32

← Older revision		Revision as of 17:26, 24 April 2012
Line 96:		Line 96:
	==[[STL Containers for Comet32]]==		==[[STL Containers for Comet32]]==

-	STL_Containers are C++ data structures for storing collections of data. They are similar to arrays but each container is designed for a different use and each has its own set of utility functions. We implemented 5 containers for IB: vector, list, map, stack, and queue.	+	Justin recapped the concept of containers, recently introduced for Comet32. STL_Containers are C++ data structures for storing collections of data. They are similar to arrays but each container is designed for a different use and each has its own set of utility functions. We implemented 5 containers for IB: vector, list, map, stack, and queue.

	The vector and the map can easily be related to IB concepts you are already familiar with. Think of a vector as an IB array but with no declared limit on the number of elements. You can add any number of elements at runtime and the vector will grow in size as required. And while for an IB array you must declare its type (string or numeric), in a vector any element may be of either type. You reference an individual element by its element number just like an array.		The vector and the map can easily be related to IB concepts you are already familiar with. Think of a vector as an IB array but with no declared limit on the number of elements. You can add any number of elements at runtime and the vector will grow in size as required. And while for an IB array you must declare its type (string or numeric), in a vector any element may be of either type. You reference an individual element by its element number just like an array.

Barb: /* STL Containers for Comet32 */

2012-04-24T17:25:21Z

STL Containers for Comet32

← Older revision		Revision as of 17:25, 24 April 2012
Line 100:		Line 100:
	The vector and the map can easily be related to IB concepts you are already familiar with. Think of a vector as an IB array but with no declared limit on the number of elements. You can add any number of elements at runtime and the vector will grow in size as required. And while for an IB array you must declare its type (string or numeric), in a vector any element may be of either type. You reference an individual element by its element number just like an array.		The vector and the map can easily be related to IB concepts you are already familiar with. Think of a vector as an IB array but with no declared limit on the number of elements. You can add any number of elements at runtime and the vector will grow in size as required. And while for an IB array you must declare its type (string or numeric), in a vector any element may be of either type. You reference an individual element by its element number just like an array.

-	You can think of a map as a good old fashioned Comet keyed file but in memory instead of on disk. Each entry in a map consists of a key and the data associated with that key. You reference an individual element by its key rather than its element number. Like a vector it grows dynamically as needed. The example of the new [[Replace]] function in the XAP2 discussion above uses a map.	+	You can think of a map as a good old fashioned Comet keyed file but in memory instead of on disk. Each entry in a map consists of a key and the data associated with that key. You reference an individual element by its key rather than its element number. Like a vector it grows dynamically as needed. The example of the new [[Replace]] function in the XAP2 discussion above uses a map to perform a merge.

	Each container type has associated functions that are designed specifically for the properties of the container. Some examples are first and last, next and prev for iteration, element counting, and push/pop functions. We would like to expand on these especially the addition of a sorting function. For all the details of our implementation check out the [[STL_Containers]] Reference on the wiki. You can get additional theoretical info by googling "STL Containers".		Each container type has associated functions that are designed specifically for the properties of the container. Some examples are first and last, next and prev for iteration, element counting, and push/pop functions. We would like to expand on these especially the addition of a sorting function. For all the details of our implementation check out the [[STL_Containers]] Reference on the wiki. You can get additional theoretical info by googling "STL Containers".

Barb: /* STL Containers for Comet32 */

2012-04-24T17:24:38Z

STL Containers for Comet32

← Older revision		Revision as of 17:24, 24 April 2012
Line 100:		Line 100:
	The vector and the map can easily be related to IB concepts you are already familiar with. Think of a vector as an IB array but with no declared limit on the number of elements. You can add any number of elements at runtime and the vector will grow in size as required. And while for an IB array you must declare its type (string or numeric), in a vector any element may be of either type. You reference an individual element by its element number just like an array.		The vector and the map can easily be related to IB concepts you are already familiar with. Think of a vector as an IB array but with no declared limit on the number of elements. You can add any number of elements at runtime and the vector will grow in size as required. And while for an IB array you must declare its type (string or numeric), in a vector any element may be of either type. You reference an individual element by its element number just like an array.

-	You can think of a map as a good old fashioned Comet keyed file but in memory instead of on disk. Each entry in a map consists of a key and the data associated with that key. You reference an individual element by its key rather than its element number. Like a vector it grows dynamically as needed.	+	You can think of a map as a good old fashioned Comet keyed file but in memory instead of on disk. Each entry in a map consists of a key and the data associated with that key. You reference an individual element by its key rather than its element number. Like a vector it grows dynamically as needed. The example of the new [[Replace]] function in the XAP2 discussion above uses a map.

	Each container type has associated functions that are designed specifically for the properties of the container. Some examples are first and last, next and prev for iteration, element counting, and push/pop functions. We would like to expand on these especially the addition of a sorting function. For all the details of our implementation check out the [[STL_Containers]] Reference on the wiki. You can get additional theoretical info by googling "STL Containers".		Each container type has associated functions that are designed specifically for the properties of the container. Some examples are first and last, next and prev for iteration, element counting, and push/pop functions. We would like to expand on these especially the addition of a sorting function. For all the details of our implementation check out the [[STL_Containers]] Reference on the wiki. You can get additional theoretical info by googling "STL Containers".

Barb: /* STL Containers for Comet32 */

2012-04-24T17:21:29Z

STL Containers for Comet32

← Older revision		Revision as of 17:21, 24 April 2012
Line 102:		Line 102:
	You can think of a map as a good old fashioned Comet keyed file but in memory instead of on disk. Each entry in a map consists of a key and the data associated with that key. You reference an individual element by its key rather than its element number. Like a vector it grows dynamically as needed.		You can think of a map as a good old fashioned Comet keyed file but in memory instead of on disk. Each entry in a map consists of a key and the data associated with that key. You reference an individual element by its key rather than its element number. Like a vector it grows dynamically as needed.

-	Each container type has associated functions that are designed specifically for the properties of the container. Some examples are first and last, next and prev for iteration, element counting, and push/pop functions. We would like to expand on these especially the addition of a sorting function. For all the details check out the [[STL_Containers]] Reference on the wiki.	+	Each container type has associated functions that are designed specifically for the properties of the container. Some examples are first and last, next and prev for iteration, element counting, and push/pop functions. We would like to expand on these especially the addition of a sorting function. For all the details of our implementation check out the [[STL_Containers]] Reference on the wiki. You can get additional theoretical info by googling "STL Containers".

	==[[CometPDF]]==		==[[CometPDF]]==