R
Riverside Software
Guest
Thanks Peter and David > An ABL application is defined by having a session manager which means it has one or more multi-session agents. Each abl application has its own db connection(s) and PROPATH. > Reasons to have multiple WebApps might be to have separate security spaces (ie /Public might have anonymous access and /Private might use LDAP or OERealm authentication). Will have another look tomorrow morning, but for example the startup parameters are defined in the session manager (the -db parameter) while propath is defined in the agent properties. For a classic appserver (only exposing .p, no REST or SOAP), do you have an example on how security can be applied differently on two different webapps ? If they both share the same propath and db connection, how can security be applied differently ? I have to admit I didn't spend a lot of time on security for now, so that may be a stupid question! >> Is there also a whitepaper on how to set-up WebSpeed applications in a "modern" way, meaning without taking care of the legacy webspeed issues ? > That's a good suggestion. > What kinds of issues do you mean? Just trying to gather initial requirements to develop / deploy WebSpeed applications using PASOE, so perhaps looking for the holy grail 
Continue reading...
Continue reading...