Welcome to the SRP Forum! Please refer to the SRP Forum FAQ post if you have any questions regarding how the forum works.
O4W
Could/Would you use HTTP_FRAMEWORKS with O4W
Would still just use the url/api/apiname calls or would you invoke differenty because it is all rbasic calls
is there a function in O4W to allow you to do that 'call'
I feel that HTTP frames works would do better web interface validation
Not sure if I am asking the correct questions.
fyI: the APIs already exist for a 3rd party written web app.
But, would like to know for future O4W apps.
I feel that HTTP frames works would do better web interface validation
Would still just use the url/api/apiname calls or would you invoke differenty because it is all rbasic calls
is there a function in O4W to allow you to do that 'call'
I feel that HTTP frames works would do better web interface validation
Not sure if I am asking the correct questions.
fyI: the APIs already exist for a 3rd party written web app.
But, would like to know for future O4W apps.
I feel that HTTP frames works would do better web interface validation
Comments
Would? Probably not, but might consider if there was an intent to completely move away from O4W.
O4W requires that you use RUN_OECGI_REQUEST. The HTTP Framework requires that you use HTTP_MCP. Thus you would need two different OEngineServer configurations to have both work together.
O4W is really designed to be an all-inclusive and tightly-coupled tool. The HTTP Framework is designed to remove this restriction and give you the freedom to develop the front end web stack separately.