Why would one choose or need RPGsp in addition to this?
Posted: Fri Apr 23, 2010 3:46 pm
Question:
This product seems to overlap RPGsp in many ways. Why would one choose or need RPGsp in addition to this?
Answer:
There is some overlap in what can be accomplished with the two products.
RPGsp is CGI-based, which means developers use the stateless Web paradigm for creating applications. For developers with prior Web experience, it is quite natural, but for someone whose background is primarily RPG, there may be a bit of a learning curve to get their head around concepts like Query String Parameters, HTTP protocols, HTML, JavaScript, AJAX, POST vs. GET, cross-browser compatibility, etc.
Profound UI encapsulates all Web concepts by using the traditional top-down RPG paradigm. It is made for the business application developer, who would prefer to have a platform like Profound UI do all the Web plumbing, rather than coding and understanding it on their own. For the traditional RPG developer, this is ideal, because with Profound UI, the RPG code looks pretty much the same as if they were to develop a green-screen app -- but now they are creating Rich UI apps.
However, there are certain lower level tasks where you may want to utilize RPGsp instead of Profound UI. For example, if you wanted to attach JavaScript events to Profound UI widgets to fire off AJAX requests, RPGsp is ideal for handling those requests.
This product seems to overlap RPGsp in many ways. Why would one choose or need RPGsp in addition to this?
Answer:
There is some overlap in what can be accomplished with the two products.
RPGsp is CGI-based, which means developers use the stateless Web paradigm for creating applications. For developers with prior Web experience, it is quite natural, but for someone whose background is primarily RPG, there may be a bit of a learning curve to get their head around concepts like Query String Parameters, HTTP protocols, HTML, JavaScript, AJAX, POST vs. GET, cross-browser compatibility, etc.
Profound UI encapsulates all Web concepts by using the traditional top-down RPG paradigm. It is made for the business application developer, who would prefer to have a platform like Profound UI do all the Web plumbing, rather than coding and understanding it on their own. For the traditional RPG developer, this is ideal, because with Profound UI, the RPG code looks pretty much the same as if they were to develop a green-screen app -- but now they are creating Rich UI apps.
However, there are certain lower level tasks where you may want to utilize RPGsp instead of Profound UI. For example, if you wanted to attach JavaScript events to Profound UI widgets to fire off AJAX requests, RPGsp is ideal for handling those requests.