Re: PlRPC vs POE as core P5EE Server
[email protected] (Aaron Johnson)
| Newsgroups | perl.p5ee |
|---|---|
| Message-ID | <[email protected]> |
I am going to second Rob on this. However I reserve the right to re-evaluate upon more input from Stephen as to how in fact this system is to be used. From what I see in his initial post I don't have enough to make an informed response, so my response is based on my gut, which tells me that I already use Apache/mod_perl in this way and it servers (pun intended) my purpose. I have dabbled with SOAP, but there really isn't any benefit to it with what I do. Aaron Johnson Rob Nagler wrote: > Stephen Adkins writes: > >>There are going to be an increasing number of cases where >>the P5EE needs a core server, separate from the web server. >>(Similar in some respects to how an EJB server is separate >>from the web server in which Servlets run.) >> > > I think the reliability/flexibility/security of Apache/mod_perl is > hard to beat. We initially had separate servers in bOP, and we > through them out in favor of using Apache for all RPC. We marshall > requests to mulitpart/form-data, so we get maximum reuse. However, > you might consider SOAP if you want more complexity. > > Remember that adding a new component type, adds complexity. The users > need to learn how to configure it. They also need to design new to > understand the difference between the "old way" and the "new way" when > implementing components. The server itself is a management problem > (start up order and other process management issues). > > Rob > > > >