http listener?

General
1

I want to receive http posts in my application.
Do i get a listener for free if I have a web viewer on my app or must i instantiate a http listener?
Examples?

2

This seems to call for a web app…

3

[quote=456464:@Brian O’Brien]I want to receive http posts in my application.
Do i get a listener for free if I have a web viewer on my app or must i instantiate a http listener?
Examples?[/quote]

The example folder has lots of this?
Examples > communication > Internet

4

You can place Aloe Express inside a desktop app as well as console/web.

5

I’d defiantly 2nd aloe express. I haven’t deployed it yet but i plan to. It’s excellent.

6

I have just finished adapting Aloe Express inside a desktop app to that:

  1. it can act as a client, or server or neither
  2. as a client, it places all SQLSelect and SQLExecute items into a JSON, zip compresses and encrypts it and sends it to the master (even itself!) via a URLconnection. Later it receives the results, decrypts the returning JSON, unzips it and turns the RecordSet JSON back into a RecordSet.
  3. as a server, Aloe receives the URLConnection, decrypts and unzips the SQL command pieces, runs them, then rebuilds a JSON with the database error boolean/code/message and another JSON for the RecordSet, zips and encrypts the lot, then sends it back via the URLConnection.
  4. I have also adapted the MBS RecordSetToJON and JSONToRecordSet methods to accept BLOB binary data. I use Encode/DecodeBase64 to handle the zipped and encrypted data to stop JSON having a coronary.

I plan to reuse this code inside the web version of the application I have created.

This will allow me to create applications that communicate with a database via Aloe Express as middleware and the desktop application knows nothing about the database brand, host, username or password.

7

i guess you speak about a pc app.
its basically a tcp socket that listening on an port for a connection.
if the connection is allowed the transfer is made via other ports that the listen port is always free.
you got the data from the other side.
the web part which send the data should look like this whereby the number is the listening port in your app.

<form action="http:/myserver:1234/process" method="post">

take into account if you have ms iis (or visual studio) or apache installed the default http/https ports are in use.
at windows use in cmd window netstat -a