Glenn, It is the same number of requests to open a file or to open/read a directory through Netbios.
But I dont read the file the traditional way so it is one step quicker the way I do it which is detailed below. I just use a require on the file name if The app was able to connect to the server. This way if the dial up user opens the application and it can not for some unknown reason connect to the Server the script will continue without fail on the version they have installed. If it can connect to the server then the data is checked to see if there is a newer version and if there is a newer version the user can select to download it now or wait until the next time they are in the office. Like I said before I will just keep doing it this way. Thanks a lot for the help. Jimmy -----Original Message----- From: Glenn Linderman [mailto:[EMAIL PROTECTED] Sent: Thursday, February 05, 2004 11:24 PM To: Jimmy Bodkin Cc: [EMAIL PROTECTED] Subject: Re: GUI output and CMD line output On approximately 2/5/2004 7:02 PM, came the following characters from the keyboard of Jimmy Bodkin: > Glenn, > > Correct but if I put the Version Number in the name. > Which I do as I create it but I put in on the server with the root name. > > I.E. File name When the program is created = root_name.v#.#.exe > File name when put on the server = root_name.exe > > Some of my users are Dialup and if I had the program read the files in this > directory and then parse the output of the exe name to determine the version > of the file. This could cause the start up of the program to be very slow > considering it is a netbios share to the server. > > If the file name is always the same then it is one cmd to the server to > retreve the info. > If I do a list of the files in the dir then it is two cmd's. I'm sorry, I guess I can't count. If the name is always the same, and you want to read it, that is "open/read/close" which may be one netbios operation or 2 or 3. (I can't remember if open is bundled in the first read, and I can't remember if there is an automatic close, so that's why I can't count. And some of those may have been optimized since I last used NetBIOS 12 years ago.) If the name is always different, it would seem to be one dir command "dir root_name.*.exe" which seems to only be one netbios operation, if I recall correctly. Especially if you only keep the current file in the "Right place", but I think a pattern match dir can return many files in one RetBIOS op. So if they are both one operation, putting the version in the name solves the problem of the extra file to manually maintain. And if open/read/close actually takes more NetBIOS operations, then it is clearly slower. I think you need to benchmark this, or at least count it. > I know that this does not seem to be that much of a difference but one > command over a dialup connection is a lot faster than two. I've used dialup enough to appreciate the difference. And it is NetBIOS operations you want to count/measure for the dialup users. So you are thinking about the right thing, but I'd appreciate if you would count the actual operations in a trace, or do a benchmark to infer the count, because from what I think I remember about NetBIOS, I think your counts are off. But it may be mine. > Thanks again for the help. > > Like I said below I think I will just have to keep using the File with the > Version info in it. > > Jimmy > > -----Original Message----- > From: Glenn Linderman [mailto:[EMAIL PROTECTED] > Sent: Thursday, February 05, 2004 4:51 PM > To: Jimmy Bodkin > Cc: [EMAIL PROTECTED] > Subject: Re: GUI output and CMD line output > > > On approximately 2/5/2004 11:32 AM, came the following characters from > the keyboard of Jimmy Bodkin: > >>Glenn, >> >>Sorry about not giving all the info. >> >>Here is the lay out of the work environment. >> >>LAN/WAN environment, individual PC's. >>Application is run local on each PC >>Latest version is on a Central Server that everyone has access to. >>Currently the application connects to the server and reads a Version file > > to > >>determine the latest release of Code. > > > Right, and a separately updated version file was avoided in my scheme of > putting the version in the filename. This separately updated version > file sounded like it was problematical to you in one of your messages. > > >>If the latest version is newer than the Version the user is running they > > are > >>prompted with a upgrade now/cancel option. >> >> >>I have all the above working. >>The trouble I have is that I want to run the application with a -v option >>and the application will tell the user its Version number. >> >>I now believe that there is no way I can do this if I want to use > > the --gui > >>option to create the exe. > > > If you really want to tell the USER its version number, Win32::MsgBox > could be the answer, like I first suggested. > > But it sounded like you wanted to tell some _program_ the version number > via STDOUT. That may not be possible, together with the --gui option, > because --gui causes there not to be a STDOUT. > > >>Thanks to all for the assistance >> >>Jimmy >> >>-----Original Message----- >>From: Glenn Linderman [mailto:[EMAIL PROTECTED] >> >> >> > > > -- > Glenn -- http://nevcal.com/ > =========================== > The best part about procrastination is that you are never bored, > because you have all kinds of things that you should be doing. > > > -- Glenn -- http://nevcal.com/ =========================== The best part about procrastination is that you are never bored, because you have all kinds of things that you should be doing.
