Scott -
There are two scenarios I can think of that describe the timing associated with editing posts.  Should the timeout be restricting how long you have the option to edit a post?  Or, should the timeout be restricting how long you have to complete the edit of a post?  
The timeout for allowing edit to posts is 5 minutes.  How we would like for that to work would be that the option would be available for 5 minutes and then you had as much time as you needed to actually edit your message and resubmit it.  
The reason we keep the edit time period short is partly because of the synchronization with NNTP and also to keep an actual record of the conversation rather than allowing users to change messages after others have replied to them and cause confusion.
The way it works right now, the timeout for editing posts is set to 5 minutes.  What the product is supposed to do is not only limit the time period that the edit option is available but to also require that all edits be submitted and completed in that time period.  The caveat here is that this is how the product is designed, but not how it is actually working.
Now, you have 5 minutes where the option to edit the message is available.  If you submit your edit after the 5 minute timeout expires you are given an error message saying your edit timeout expired, but the edit is actually submitted to the system.  This is a known issue in the system and it is on the list to fix in a future release.  An example demonstrating this is your message that you posted at 31 minutes past the hour, but edited at 39 minutes past the hour.
http://forums.ni.com/ni/board/message?board.id=330&message.id=6699#M6699
Hope I didn't confuse things more!
Which way do you prefer the design to work?  Limit how long the option is available or how long it actually takes to submit it?
Thanks!
					
				
			
			
				
	Molly K.
Web Support & Operations Manager
National Instruments