P
Peter Judge
Guest
I don’t know about EULAs but will try to answer some bits. WebHandlers only work on PASOE and only on 11.6.0+, when the WEB transport was introduced. They do not work on the REST or any other transport. At a bare minimum you need an implementation of a OpenEdge.Web.IWebRequest and an implementation of a Progress.Web.IWebHandler and some configuration (properties) to use that WebHandler for a particular (OE-) Webapp. We try to code to interfaces as far as possible but (as Mike Fechner noted elsewhere on these forums) that doesn’t guarantee that we won’t break backwards compatibility. PSC ships a few implementations (for a variety of purposes). I’ve done a couple of session on webhandlers at PUGs over time. The slides at onedrive.live.com/ have the basics. The sources are available in $DLC/src/netlib/OpenEdge.Net.pl , and are for that version of OE. We don’t typically provide specs. There is some API doc at OpenEdge API Code Documentation . There’s no technical reason preventing you from shipping/deploying an entire ABL “runtime environment” – by which I mean a predefined set of rcode that your application uses. You can use the -baseADE parameter to point to a directory containing a set of PL files, or set it to blank to prevent the AVM from adding the standard default PROPATH entries (eg. $DLC/tty). The compatibility of this rcode would obviously be subject to the AVM’s version (and features etc). Not sure as to what you mean by part of an SDK (but I’m interested in what you’d want in/as one). Also, deployment and versioning of ABL services (and other parts of an application) to PASOE is something we’re working on at the moment – we’ll be asking about some of these on the CVP forums ( OpenEdge CVP - Progress Community ) .
Continue reading...
Continue reading...