OK, now that 2.5.3 is out the door and appears to be quite stable, I can go back to giving you Development updates on 3.0. It will be awhile before it is released, but I thought you might like to know that...

In Sesame 3, there is now a menu choice to allow an end user to change their own password.

Hammer, this thread is now at 9 pages, with a number of tangents.  How about putting together three "summary" posts:

1) New features already added or in process

2) Suggestions that will not be developed

3) Suggestions still open for consideration

Hammer wrote on Sep 24^th, 2012 at 2:50pm:



  Any chance we can get some reporting / documentation for security?  The ability to create a file or print out of the groups with permissions, the users by groups etc...

I know it must be the pits that every time you tell us about an incredible new feature we ask it to do more, We love what you give us we just like offering other things for you to think about.

Thanks for the new user changeable  password feature!

Sesame 3 has a new search syntax called PLAIN that you can turn on in the sesame.ini file. It runs all searches as if you had used .. before and after without needing the wildcards. So, if you search for MAR in a field, it will behave as if you searched for ..MAR.. and return MARY, DELMAR, and AMARETTO.

Going forward a lot things are changing. Time when we used to snail mail the paper bill and invoice, then we could prepare it on computer and fax it. Now they want the form filled out the website and submit. All data also has to be sent using either sFTP or HTTPS in the  format they want. It used to be text (csv), then HL7 or other proprietary format and now in XML. 

Sesame has provided users and developers with various tools to accomplish the job and especially with @Shell ( ), @ASynchShell ( ), CreateAProcess ( ) and RedirectProcess ( ) commands, we can use outside commandline utilities to meet the pressing demand in the ever-changing environment.

With the web-interaction in the form of filling out cgi forms and submitting data, the most of the sites use SSL and that is where Sesame native commands fall short at present, however, one can use outside utilities to overcome the gap.  I am confident that in the upcoming version 3, the forward looking Lanticans must have addressed to this needs and provided tools to deal with this growing needs.

I was going through cURL manual and FAQ to meet some my present needs and to my surprise, this utility is free to be utilized in any commercial product.  Incorporating this would definitely enhance Sesame to take care of SSL and other web-interaction chores.

Naturally my curiosity is growing to find out how Sesame will address to this growing need and any plan to incorporate cURL like utilities instead of re-inventing wheels?

Mark, thanks for explanation. I am sure that with the available commands and support from Sesame Support Team and Lanticans, we will overcome anything and everything thrown at us in terms of emerging technology.  Thanks again.

There is continuous progress, but no release date set. My latest work has been on a built in HTTP proxy, with hopes of allowing Sesame3 to work on a web server without the need to tunneling.