Arvind Srinivasan wrote: > Basant Kukreja wrote: > > >> Note: Redhat/Fedora follows the above approach to have single apr library >> which >> have threads enabled. >> >> > > What about the other build artifacts such as apxs, build/*mk etc - are there > 2 > sets (1 for prefork and the other for worker) or just one? i.e. How does an > Apache module developer using Redhat/Fedora go about compiling/developing > his/her module for prefork vs worker? > > Common HTTpd distributors ships prefork as the default and accordingly all build artifacts reflect the prefork model. Since the back end APR is compiled in multi-threaded mode, these modules can be used with worker MPM as well. > Also, do distributions that ship both prefork and worker mpms of Apache, also > ship PHP built for prefork as well as worker? > > mod_php is associated with prefork MPM . This dependency is captured as part of RPM dependency. > The current proposal/plan to ship multiple MPMs of Apache 2.2.x does affect > the > downstream modules built around Apache both in terms of file layout and the > bits that'll be in SXDE. > > What about 32-bit Apache vs 64-bit Apache? If we plan to do this in the > future,it will mean that we package the build artifacts for 32-bit and > 64-bit > under separate directories. > > I am afraid so.
thanks sriram > > _______________________________________________ > webstack-discuss mailing list > webstack-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/webstack-discuss >
