rejetto forum

Software => HFS ~ HTTP File Server => Beta => Topic started by: rejetto on February 11, 2009, 05:50:20 PM

Title: Testing build #223
Post by: rejetto on February 11, 2009, 05:50:20 PM
published while driving

download @ www.dovedove.it/hfs/hfs223.exe

what's new
+ new template symbols: %now% %item-added-dt% %item-modified-dt%
+ {.time.} supports new parameter "when" to use a different time than the current one
+ new template macro: trunc
- solved some problems when adding many single files
- "open it" was not working if the path had spaces http://www.rejetto.com/forum/index.php?topic=6632.msg1040608#msg1040608
- sometimes the editor didn't run http://www.rejetto.com/forum/index.php?topic=6632.msg1040616#msg1040616
- deletion and {.postvar.} broken in build #222 http://www.rejetto.com/forum/index.php?topic=6632.msg1040575#msg1040575
- deletion never worked with some features enabled http://www.rejetto.com/forum/index.php?topic=6632.msg1040575#msg1040575
Title: Re: Testing build #223
Post by: Ranger on February 11, 2009, 06:17:15 PM
Thanks rjetto!

Any hope of supporting this? (or to-do)

http://www.rejetto.com/forum/index.php?topic=6618.0
Title: Re: Testing build #223
Post by: hvdb on February 11, 2009, 08:33:18 PM
updating results in using beta 220 ...

must be an error.
Title: Re: Testing build #223
Post by: Mars on February 11, 2009, 11:48:39 PM
1) :o  A thing which you had promised is missing:

result:=result+xtpl(p, [ '%bread-url%',e,'%bread-name%',ad[i],'%bread-idx%',inttostr(i)  ]);

2)  ;D thank you for:  tpl-editor=C:\Programmi\PSPad editor\pspad.exe

3)   :'( By wanting to make court, you did not envisage all the eventualities, put one # in the middle of a filename and creating md5 which  is associated with him, and then try to delete  this file by using the template by default.

by example,  rejetto#maximo.bad  cannot be destroyed
  the good code



       s:=getTill('#!md5', decodeURL(data.postvars.valueFromIndex)); // omit #anchors

4)  ??? Out of necessity: here are three new macros to add to the next build
Quote
    if name = 'is substring' then
      trueIf(ansiContainsText(par(1), p));

    if name = 'count substring' then
      result:=intToStr(countSubstr(pars[0], par(1)));

    if name = 'pos substring' then          //mars 2009
      result:=inttostr(pos(pars[0], par(1)));

    if name = 'chop start' then     //mars 2009
      begin
      result:=par(1);
      result:= chop(pars[0], result);
      end;

    if name = 'chop end' then       //mars 2009
      begin
      result:=par(1);
      chop(pars[0], result);
      end;
    if name = 'and' then
      allLogic(TRUE);

   '{.pos substring|rejetto| On the forum, rejetto is the absolute boss .}'   return '15'

   '{.chop start|rejetto| On the forum, rejetto is the absolute boss .}'       return 'On the forum, '
   
   '{.chop end|rejetto| On the forum, rejetto is the absolute boss .}'         return ' is the absolute boss'

 ;)

On the forum, rejetto is the absolute boss......
But in the sources of hfs, Mars will defend  his beefsteak

 ;D ;D ;D ;D
Title: Re: Testing build #223
Post by: rejetto on February 12, 2009, 12:33:22 AM
1. ugh, next build ;)

2. i'll exclude the ini from backups ;)

3. no mars, my idea is ok: i'm getting the file as an url, and # is a special character. The bug is the fact i was splitting after decoding. In next build i will do it before, and it will work. ;)

4.
pos substring: i wonder why i didn't do it before. i think anyway that the name 'pos' should be adequate. do you agree?

chop start: is the same as {.substring||$1|$2.}
very little difference, superfluous IMO.

chop end: is the same as {.cut|{.add|1|{.length|$1.}.}||{.substring|$1||$2.}.}
this is more different, at a glance.
but, from a user point of view, the only difference with substring is that first parameter is not included in the result. very little. i will just expand 'substring' with an option 'include', that will let you specify what to include in the result.
so, from next build, it will be the same as {.substring|$1||$2|include=none.}
include=0 will work as well
Title: Re: Testing build #223
Post by: rejetto on February 12, 2009, 12:37:56 AM
updating results in using beta 220 ...
must be an error.

no one else did report such problem. i guess you just made a mistake.
did you use automatic update?
Title: Re: Testing build #223
Post by: hvdb on February 12, 2009, 06:48:23 AM
yes i'dd use beta 220. from that one i auto updated it to 223.
but it brought me back to 220.

if no one else triggered that prob, it must be on my side , although i dont know how.
Title: Re: Testing build #223
Post by: hvdb on February 12, 2009, 06:58:59 AM
Did update again, it works!

hope this was a one time only never had any problems with your updates.
Title: Re: Testing build #223
Post by: rejetto on February 12, 2009, 11:32:55 AM
well, if you used the autoupdate, i guess it's an occasional problem of it. it's not perfect ;)
i supposed it was you if you did it manually.

published while driving

i meant i was really driving my car.
my laptop was on my side, running the publishing procedure, connected via gprs.
i was occasionally interacting at the stop lights.
i had to run out of the office :)
Title: Re: Testing build #223
Post by: luca69 on February 12, 2009, 12:39:56 PM
Quote from: rejetto
published while driving

i meant i was really driving my car.
my laptop was on my side, running the publishing procedure, connected via gprs.
i was occasionally interacting at the stop lights.
i had to run out of the office :)

 :o :o :o :o :o :o :o
You need an upgrade to HSDPA  ;D
Title: Re: Testing build #223
Post by: rejetto on February 12, 2009, 12:52:57 PM
i have it.
just to be understandable by more people ;)
Title: Re: Testing build #223
Post by: Fysack on February 12, 2009, 03:35:56 PM
my laptop was on my side, running the publishing procedure, connected via gprs.
lol, you are a bussy man rejetto  :)
Title: Re: Testing build #223
Post by: MarkV on February 12, 2009, 10:27:04 PM
well, if you used the autoupdate, i guess it's an occasional problem of it. it's not perfect ;)
I have a machine that's having problems with the autoupdate... because it's too slow.  ;D Only 80486-100MHz... The three seconds ping is not long enough to close HFS, so I get 'Access denied' Retry Abort Fail message in the batch. Unfortunately it's hardcoded.
Title: Re: Testing build #223
Post by: SilentPliz on February 12, 2009, 10:34:00 PM
well, if you used the autoupdate, i guess it's an occasional problem of it. it's not perfect ;)
i supposed it was you if you did it manually.

published while driving

i meant i was really driving my car.
my laptop was on my side, running the publishing procedure, connected via gprs.
i was occasionally interacting at the stop lights.
i had to run out of the office :)

   
Not panic ... it is not dangerous to phone call in car in Rome  :D
Title: Re: Testing build #223
Post by: Mars on February 12, 2009, 10:37:09 PM
The motor traffic jam,  is it rejetto who has made this? ;D
Title: Re: Testing build #223
Post by: rejetto on February 13, 2009, 10:19:19 AM
lol to it all
Title: Re: Testing build #223
Post by: rejetto on February 13, 2009, 07:37:20 PM
drohr moved to http://www.rejetto.com/forum/index.php?topic=6656
Title: Re: Testing build #223
Post by: Domen ltd on February 16, 2009, 08:29:47 AM
Please check this. HFS 223 constantly reads the same data from disk! Found with Winternals Administrator's Pak - Filemon Enterprise Edition.
Title: Re: Testing build #223
Post by: rejetto on February 16, 2009, 10:04:00 AM
it's a known behavior: it checks if the filestamp has changed.
in such case it will re-load it.
Title: Re: Testing build #223
Post by: Domen ltd on February 16, 2009, 02:34:08 PM
it's a known behavior: it checks if the filestamp has changed.
in such case it will re-load it.

The HFS 2.2e(154) does not have this feature? Can I turn off it?
Title: Re: Testing build #223
Post by: Mars on February 16, 2009, 02:38:01 PM
with filemon you can use filters to exclude hfs reports
Title: Re: Testing build #223
Post by: Domen ltd on February 16, 2009, 03:03:47 PM
Mars. I know how to use filemon. ;) Is it necessary to check filestamp so often? That's a question.
Title: Re: Testing build #223
Post by: rejetto on February 16, 2009, 03:04:19 PM
The HFS 2.2e(154) does not have this feature? Can I turn off it?

that feature is "external template file".
if you want to disable it, the only way is to set the default template.

Mars. I know how to use filemon. ;) Is it necessary to check filestamp so often? That's a question.

i may change it to once per second. what's the gain?
Title: Re: Testing build #223
Post by: Domen ltd on February 16, 2009, 07:04:39 PM
Rejetto. This method checks if the external template file has changed? Am I right? So, why dont to check in that time when a request arrives to the server from a user?

P.S. Sorry for my bad English.
Title: Re: Testing build #223
Post by: rejetto on February 18, 2009, 02:34:27 AM
yes, it seems a good idea
Title: Re: Testing build #223
Post by: Fysack on February 19, 2009, 06:41:13 PM
P.S. Sorry for my bad English.
You speak perfect Englich Domen ltd  8)