Hi Tim

Just wanted to say "Thank You" for such a great product. (EWB).

1. Moving  projects from 2.05 to 2.06 was painless...

2. The speed improvement over 2.05 is really good !

I just need built in  "SSL" Support.

(its what virtually all customers I talk to - ask about)

If we could get that soon... that would be fantastic.

best regards

Kamran

Tim:

Trying to be helpful - just thought I would throw this out there.. Have you thought about using StreamSec Tools 2.x to implement SSL.

From StreamSec website:

StreamSec Tools 2.x is still actively maintained and updated, due to it's widespread use as a SSL/TLS solution for e.g. RealThinClient SDK, NexusDB, kbmMW, Indy and Ararat Synapse.

Walter

Bruno,

<< Tim.. latest update working fantastic, thanks. EWB footprint at Environment Canada continues to increase! >>

That's always great to hear.

<< 1. Code completion

.. makes it easier and faster for 'newbies' to explore a new language, but also for the veterans.. who start forgetting stuff. Using this since '95 (Delphi 1), we become spoiled, I suppose >>

Yeah, this will probably sneak in sooner than expected, like the Find Declaration functionality.  The only holdup is that I need to get background compilation in place.

<< 2. SSL support on the EWB server >>

This is definitely coming next.

Tim Young
Elevate Software
www.elevatesoft.com

<< Tim, you did a really great job.Thanks ! >>

Thanks.

<< The only feature I'm missing is the code completion to work faster and get my beer sooner >>

Yeah, as I replied to Bruno, this needs to get done.  The component library/run-time keeps growing and getting more complex, which just makes the problem worse for new developers.  Plus, we're hoping to bring non-Object Pascal developers into the fold, so to speak, and it's necessary for fast adoption.

One of the other items high on the list in the compiler is proper set support.

Tim Young
Elevate Software
www.elevatesoft.com

Kamran,

<< Just wanted to say "Thank You" for such a great product. (EWB).

1. Moving  projects from 2.05 to 2.06 was painless...

2. The speed improvement over 2.05 is really good ! >>

Good, I'm glad that you're seeing better performance.  It took about 1 1/2 months to get that all straight.

<< I just need built in  "SSL" Support. >>

Yep, it's coming in 2.07.

Tim Young
Elevate Software
www.elevatesoft.com

Walter,

<< Trying to be helpful - just thought I would throw this out there.. Have you thought about using StreamSec Tools 2.x to implement SSL.

From StreamSec website:

StreamSec Tools 2.x is still actively maintained and updated, due to it's widespread use as a SSL/TLS solution for e.g. RealThinClient SDK, NexusDB, kbmMW, Indy and Ararat Synapse. >>

Thanks, I'll check it out.  Any such information is always welcome.

For right now the plans are to continue with OpenSSL. I've already got the bindings in place, and I would like to use it with our other products for encryption/SSL connections, which isn't an issue due to its open source nature.

Tim Young
Elevate Software
www.elevatesoft.com

Tim wrote:

<< For right now the plans are to continue with OpenSSL. I've already got the bindings in place, and I would like to use it with our other products for encryption/SSL connections, which isn't an issue due to its open source nature. >>

Wasn't this a major problem with the MySQL effort? That the open source and multiple developers coding led to too many issues to implement an EWB / MySQL integration? Do you anticipate similar challenges here? Or, no - does not apply.

Trinione,

<< Wasn't this a major problem with the MySQL effort? >>

It wasn't MySQL, it was the PHP APIs for MySQL.  Specifically, the PDO and MySQLi APIs (the other APIs are deprecated).  They were lacking important features that are necessary for generic database APIs.  Things like easy and accurate ways of determining the types of parameters for SQL statements and the types of columns in result sets. Keep in mind, this is with a PHP database layer for EWB that *already worked* with ElevateDB.  Why ?  Because the ElevateDB PHP Extension implements *all* of this functionality without any weird missing bits or oddball "gotchas".

There were "code smells" all over the place. For example, with the MySQLi API, it was impossible to get accurate information on the actual character-length of string columns that used UTF-8 as their collation, so you had to take a byte-length value and divide it by 3 as a "workaround".  This one actually might be a MySQL issue, but still...you don't deal with this crap with ODBC, ADO, or other types of database APIs.

By the time I got 2/3-3/4 of the way through the PHP implementation, my concern meter was pegged and I suspected that the PHP implementation was going to be a support problem, due to these weird workarounds.

<< That the open source and multiple developers coding led to too many issues to implement an EWB / MySQL integration? Do you anticipate similar challenges here? Or, no - does not apply. >>

No, it doesn't apply here.  OpenSSL is *the* standard library for SSL endpoints on most platforms. There are books written about it, and it is well-documented and feature-complete.  The Stunnel software that we recommend for use with the EWB Web Server right now uses it.

Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

> No, it doesn't apply here.  OpenSSL is the standard library for SSL endpoints on most platforms. There are books written about it, and it is well-documented and feature-complete.  The Stunnel software that we recommend for use with the EWB Web Server right now uses it.

If you need any info, I have an expert contact who could probably help. He does one of the OpenSSL DLL builds, and integrates it into a Delphi internet library.

--

Matthew Jones

Matthew,

<< If you need any info, I have an expert contact who could probably help. He does one of the OpenSSL DLL builds, and integrates it into a Delphi internet library. >>

If it's for the Windows builds here:

https://opendec.wordpress.com/tag/openssl/

please tell him that he's doing great work and we'll be making a donation shortly to help with the costs of the site and his time.  We've been using those builds in EWB for about a year, and I keep forgetting to donate.

Tim Young
Elevate Software
www.elevatesoft.com