I'm about to start cracking on the accessors that provide get/set access when in reality they not be allowed to set. I'll deal with those that can't be set due to thread-safety. I have a few ideas. But there are a few that I'm not sure about. The first one I happened to spot is port() from APR::SockAddr. I can't think of how one can possibly need to change the port number after creating the socket. That's obviously true for apps running under Apache, but I'm not sure about external use. I guess there is no harm if we disable it now, and provide in the future if we find out that there is indeed a need to allow that. We won't break any backward compatibility by adding set set ability post API freeze. What do you think?
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
