Edwin Yip

This library fills the gap of the missing of a real powerful template engine in the Delphi community. DMustache is good, but it's logic-less. I'm not talking about it's bad - on the contrary, it's good for its use cases, but we need more powerful scripting in other use cases. Had been working with the developer for XE4 compatibility few days ago (initially more modern language features were used), and he was able to quickly get thing sorted out without an XE4 compiler. Really impressed!

IIRC SQLite, Lua-JIT, the new PHP, all achieved good performance by bytecode compiler/executor (JIT).

Check https://github.com/brendangregg/FlameGraph, the flame graph is very very cool and intuitive for showing the details of the performance of the call stacks! Not sure if that technical can be applied to Delphi, it seems to be getting the statistics data from DTrace. @Arnaud Bouchez , it'll be amazing if we can see how our web service methods perform like that :D

Hello Graham, I'm trying the `SendEmail` method with the Indy http client, and got the `HTTP/1.1 505 HTTP Version not supported` error. While I'm searching for the solution, do you have any hints? Thanks! I added a github issue here so that it's easier to track it.

Hello Graham, I created an IAM user along with an access key, the VerifiedSenders project returned the correct list! Will try email sending later. BTW, do you happen to know with SES, if I will face any anti-spam or 'credit scores' issue if I suddenly starting sending email to a lot of target emails?

Thanks Graham! The 'GetVerifiedSenders' sample project can be built without any issue! Now trying to run it. In the code you have a hint about creating the SMTP credentials in the 'SES->SMTP Settings` AWS SES console. Are you sure that is right? IIRC the SMTP username/password are for SMTP access only, but ksSES is accessing SES via HTTP? Explorer the SES console now...

Wow, that's great! I hope some day I can contribute a mORMot http client. Looks like your project can be used as a foundation for implementing various REST client for various web APIs.

No, it auto-completes the historical (previously used) paths, but not all actual paths in the disk.

Hello Graham, Just tried it - it seems that the SHA256 hasing and URL encoding/decoding still depends on the `Net.*` units of newer Delphi. Maybe still have to abstract out a `IUtilityService' interface? :D

Thanks for your constant effort! One enhancement suggestion - Add path auto-complete for GREP Search -> Directories

You are fast Graham! I'll check it ASAP!

That's Great! Great! Great Graham!

Hello Graham, in case you have any uncommited changes for ksSES please commit it. In a few days I'll add old version support if you haven't done that by that time :) My idea is to abstract out a general 'IHttpClient' so that it can be replaced by Indy or mORMot.

I will try and test it immediately once you added Indy support :)

Thanks Graham!

It's only a single file so it might make sense in this case, but we usually have to consider not making any duplicate, because it's hard to sync with new changes in the other library.

I think even if the Synapse library allows you to redistribute Synacode.pas, it's not a good practice to do that, but instead, you should just state the dependency of Synapse in the readme file. Just my 2 cents.

Congrats for the new product. When will the 'for one developer' edition come out? I might find a use of it in the future.

Thanks! Definitely it'll be useful to the rest of us! Actually I've cloned your old version of ksSES to my local computer, before it's somehow disappeared like ksStripe :D There is a file called synacode.pas which is missing from the new version you've just published, I assume it's no longer needed. Update 1: First try: Just FYI - like ksStripe, it requires the new http client introduced since XE7 :)

Let me explain, usually after a customer bought a software, s/he actually bought a license key, right? So how the license key is delivered to the customer? We usually send it through email, with the payment processing platform I've used in the past, the license key delivery is done by their email system, which is usually more reliable then ourselves because it can usually go through the spam-filtering system all around. I'm also using SES, but through the SMTP interface. I remember with SES, all the target email addresses have to be approved by the SES system, maybe that's because I'm using the free plan, not sure...

Thanks! I confirm it compiles with XE4

@Graham Murt, would you share with us all your tick boxes? Since Stripe only handles the payment, I assume, if you write desktop software, you'll have to send license keys to the customers? One difficulty I foresee will be, although we can implement our back-end server for generating and sending activation/license keys, this is not the difficult part, the question will be - which reliable email sending service to use?

Same here

@Graham Murt, before using Stripe, have you used other payment processor such as FastSpring? How do you compare them? Thanks!

Agree that Indy is more generic, but I guess Indy needs OpenSSL in order to support httpS ( I guess Stripe needs https, not sure)?