Lasewing Server Question - POST Items

I was able to get the Lacewing Web Server working and I was able to send POST information from the web page to the MMF Program/Lacewing Extension. Now the issue is sending sending information in the reverse direction.

I see we could build a webpage and send it back to the browser using MMF/Lacewing. Is there a way for the Lacewing to "set the POST item field information" instead of just reading it?

Let say when I click a submit button on the webpage it does a POST to Post Item MESSAGE with the text "Hello". Now on the server MMF/Lacewing is able to access post Item MESSAGE and perform some calculation or make a decision. Now I want the POST MESSAGE item to read "Got Hello Message". Then on the webpage I could code to have the POST Item read when the webpage is loaded and a dialog box displayed saying "Server got Hello Message"

By setting the POST Item, I am able to use HTML, Javascript or a MMF webpage app to get the message, make a decision and display a dialog box. Now I have the ability to add MMF scripting to both the webpage and the server for example.

Perhaps there is a better way. Any ideas??? Any suggestions???

To continue my question, I would like to write a mmf web app to mainly read the MESSAGE when the webpage is loaded and display alert, warning or information messages to the browser user for example. So on first loading the MESSAGE is blank. When the submit button is pressed and without reloading the webpage a dialog appears saying server got the message. This happens because it MMF web app is rechecking the MESSAGE item and taking action as needed.

No HTTP server can set post data being sent back to the client - it's the wrong direction! What you can do is generate some extra javascript to open a message box with your response, or just show in the page like most servers do. Javascript message boxes should be used only for things that can be done clientside and that the server need not be bothered with.

Can the webserver keep track of the session information? If I have 5 different people using the web server how can it track where the requests came from? For example to prevent a man-in-the-middle attach?

You can access the session data just fine and it can always differentiate clients. You can also get and set client specific data (though I think in this version you can only get the data and not set it, which is useless)

I wanted to be able to use MMF to create a web plugin for the webpage that gets a code from the webserver/mmf. I see that I can send POST information to the webserver and have MMF "actions" to read the POST information and carry out a decision making process. I can also see how I can create a webpage to send back to the browser. Very cool. But I really just wanted to have a MMF web plugin that would get a code from the server and then could display a dialog box with a message like "logon failed". Yes I know this can be done with javascript but I was hoping to be able to do it with a MMF plugin so I don't have to resend a webpage each time, like JSON does I believe. I am unaware of if the MMF plugin has any way of accessing any of the webpage fields like a hidden field like "MMFErrorCode" or "MMFErrorMessage" or any way of triggering certain actions of the browser webpage like clear fields "Username" and "Password".

I guess javascript on the client might be the only solution. Well I really like the WebServer after I got the sample file and figured out how to serve up a website with it. I have not tested the digital certificates but plan to.

From what you want to do the way you want to do it, I'd say that the webserver is the wrong tool for the job. The Lacewing Relay Client is ported to Flash with the minimal functionality you need, so you just need to host the Lacewing Relay Server.

I there any reason I could not host both the webserver on lets say port 6160 and the relay server on port 6161?

No, you could do that just fine. But what's with the strange ports? HTTP is usually port 80 and Lacewing is usually port 6121.

I can redirect port 80 to the other ports. So on the web it looks like everything is using port 80 reducing the number of ports I have to open. Another option is using No-IP to redirect port 80, or using a different webserver to secure port 80 and again redirect port 80 to the other ports if the request is from my Lacewing server application.