What you want is a CPRS designed with modern considerations. Many websites are written with non-concurrence built in. I.e. the application asks the server for information, and then continues to work as best it can until the server sends the info back. CPRS, on the other hand, is mostly written such that the client app asks the server for into, and stops and waits for a reply. This is fine on a network with low latency -- but not so great for a web situation.
All that needs to be done is a complete rewrite of CPRS. No prob, 'eh?
Kevin