Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 10 of 14 total
Thread Server To Server Communication With EWB?
Tue, Oct 23 2018 11:13 PMPermanent Link

Frederick Chin

I am writing an app to communicate with a payment gateway and there is a requirement to allow the gateway's server to communicate directly with my web server.

They gave examples of using ASP, Java and PHP.

Can I use EWB instead for this purpose or do I need to use one of the above?

--
Frederick
Tue, Oct 30 2018 2:26 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Frederick,

<< I am writing an app to communicate with a payment gateway and there is a requirement to allow the gateway's server to communicate directly with my web server.

They gave examples of using ASP, Java and PHP.

Can I use EWB instead for this purpose or do I need to use one of the above? >>

Sure, if you use a web server module or some other form of back-end code.  What you need, above all, is typically an HTTP client component that can make the relevant HTTP calls to the payment gateway on the server-side.

I will have an example of this once EWB 3 is out.  Currently, at Elevate Software we process payments manually but are converting over to an automated method early in 2019.

Tim Young
Elevate Software
www.elevatesoft.com
Tue, Oct 30 2018 6:07 PMPermanent Link

Steve Gill

Avatar

Hi Frederick,

<< I am writing an app to communicate with a payment gateway and there is a requirement to allow the gateway's server to communicate directly with my web server.

They gave examples of using ASP, Java and PHP.

Can I use EWB instead for this purpose or do I need to use one of the above? >>

The way I do it is the EWB app passes the information to a PHP script on a web server, which then connects them to PayPal.  Once payment has been processed they are taken to a web page on my website telling them that their order has been processed, etc.

When PayPal processes the payment it calls a PHP script on my server that then adds the customer to a customer database (which also gives them access to a customer portal - another EWB app), generates a licence for the program they purchased, and sends them an email, as well as some other things.

= Steve
Wed, Oct 31 2018 10:38 AMPermanent Link

Frederick Chin

Tim,

/*
Sure, if you use a web server module or some other form of back-end code.  What you need, above all, is typically an HTTP client component that can make the relevant HTTP calls to the payment gateway on the server-side.
*/

Is one of the following flow correct?

Payment gateway server --> EWB app --> Web server module --> Payment gateway server

or

Payment gateway server --> EWB app --> Web server module --> EWB app --> Payment gateway server

I tell the payment gateway provider to call my EWB app's HTML page instead of using their ASP, PHP or JSP examples.

--
Frederick
Wed, Oct 31 2018 10:43 AMPermanent Link

Frederick Chin

Hi Steve,

/*
The way I do it is the EWB app passes the information to a PHP script on a web server, which then connects them to PayPal.  Once payment has been processed they are taken to a web page on my website telling them that their order has been processed, etc.

When PayPal processes the payment it calls a PHP script on my server that then adds the customer to a customer database (which also gives them access to a customer portal - another EWB app), generates a licence for the program they purchased, and sends them an email, as well as some other things.
*/

I noticed that you are still reliant on PHP script as an intermediary to accept calls from your EWB app and from Paypal. Is there a reason why a web module or EWB app cannot be used in place of PHP?

--
Frederick
Wed, Oct 31 2018 3:47 PMPermanent Link

Steve Gill

Avatar

Hi Frederick,

<< I noticed that you are still reliant on PHP script as an intermediary to accept calls from your EWB app and from Paypal. Is there a reason why a web module or EWB app cannot be used in place of PHP? >>

The web server is Linux.  I'm waiting for EWB 3 to be released and then I'll move it all over to a Windows web server.  I have a lot of backend systems and I don't want to write them for EWB 2 and then have to rewrite them for EWB3.

= Steve
Thu, Nov 1 2018 5:42 AMPermanent Link

Matthew Jones

Steve Gill wrote:

>  web server is Linux. ... move it all over to a Windows web server

I hope that the announcement that ARC is going to die in Delphi means that EWB server will be more easily ported to Linux, and in particular (for me), containers. By having a common memory management system, services will be a lot easier to have on both systems, and we can then choose.


--

Matthew Jones
Mon, Nov 12 2018 2:23 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Matthew,

<< I hope that the announcement that ARC is going to die in Delphi means that EWB server will be more easily ported to Linux, and in particular (for me), containers. By having a common memory management system, services will be a lot easier to have on both systems, and we can then choose. >>

Yes, it will mean this (I am just ecstatic over the decision to get rid of ARC).

I just completed the MacOS port (32-bit now) for EDB, and that includes all of the POSIX layer (which is most of the required functionality), and that will be coming out in EDB 2.29 this week.

The EWB3 web server will be getting MacOS/Linux support within a month of the initial release.  The main holdup with doing it in the initial release is the OpenSSL layer (currently, all of the EWB3 web server crypto is WinCrypt).

What this all eventually means is that EWB3 will be able to have a web/application server that works
on all major platforms, along with both web and native, front-end components for accessing the web server on all major platforms.

So, be sure to purchase/upgrade to Rio 10.3 ASAP !

Tim Young
Elevate Software
www.elevatesoft.com
Mon, Nov 12 2018 2:27 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Frederick,

<< Is one of the following flow correct?

Steve's description is the correct flow.  The main thing for PCI compliance is that the CC information *cannot* hit your web server in any way, shape, or form.

Tim Young
Elevate Software
www.elevatesoft.com
Mon, Nov 12 2018 2:48 PMPermanent Link

Mark Brooks

Slikware

Avatar

Tim Young [Elevate Software] wrote:

<<I just completed the MacOS port (32-bit now) for EDB, and that includes all of the POSIX layer (which is most of the required functionality), and that will be coming out in EDB 2.29 this week.>>

Hang on Mr Young ............. are you saying that EDB 2.29 can run on a Mac, server and admin tool? Seriously?

<<The EWB3 web server will be getting MacOS/Linux support within a month of the initial release.  The main holdup with doing it in the initial release is the OpenSSL layer (currently, all of the EWB3 web server crypto is WinCrypt).>>

And then EWS too? I know it's nearly Christmas but this is ridiculously good news!  

<<What this all eventually means is that EWB3 will be able to have a web/application server that works
on all major platforms, along with both web and native, front-end components for accessing the web server on all major platforms.>>

Ok. So all we need now is a Mac IDE and I can be done with the unruly beast that is "Windows" forever!
Page 1 of 2Next Page
Jump to Page:  1 2
Image