List:Internals« Previous MessageNext Message »
From:Sasha Pachev Date:June 23 2001 11:25pm
Subject:Re: MySQL SNMP
View as plain text  
On Saturday 23 June 2001 12:45, Russell E Glaue wrote:
> Has anyone thought about adding SNMP support into MySQL?
> Is anyone out there currently working on something like this?

I've thought about it, but this is how far I went - just I thought during 
lunch. I had not even shared it with other members of the team.

Adding SNMP support would definitely be a good idea. If you want to go ahead 
and do it, we are very likely to accept the patch ( although the final word 
rests with Monty on this). To increase the chances of your patch making it 
quickly into the distribution:

* use BitKeeper ( this will make it trivial for us to add your patch - we can 
just pull it from your repository, and this will also make it very easy for 
you to always have your sources up to date)
* put as much of the new code it a new file as possible, and modify the 
existing code as little as possible
* make sure the code is thread safe. If you are not sure if some external 
library call is thread safe or not, add a mutex around it if there is a 
chance that two threads may call it at the same time
* do not use exceptions
* do not use dynamic casts
* do not use calls to libstdc++ ( eg, iostreams and STL)
* use my_malloc()/my_free() to do memory allocation
* overall, avoid calls to libc - instead use their portability equivalents in 
mysys/ - eg. instead of open()/close() call my_open()/my_close()
* if you need some "power tools" ( hash, dynamic array, dynamic string, 
linked list, memory pool, etc), just ask - we will tell you where they are in 
the source
* it has to at least not break anything when compiled on Windows ( the use of 
my_* calls usually takes care of it)
* after you've written a bit of code, send it to us for review, and repeat 
the procedure frequently

If the above is followed, we are very likely to take the patch the way it is. 
If those rules are not followed, we may still take it, but then we have to 
spend a lot of time fixing it up, which will cause a big delay.

-- 
MySQL Development Team
For technical support contracts, visit https://order.mysql.com/
   __  ___     ___ ____  __ 
  /  |/  /_ __/ __/ __ \/ /   Sasha Pachev <sasha@stripped>
 / /|_/ / // /\ \/ /_/ / /__  MySQL AB, http://www.mysql.com/
/_/  /_/\_, /___/\___\_\___/  Provo, Utah, USA
       <___/                  
Thread
Perl + MysqlDana Prescott Kennedy Powers30 Mar
  • Re: Perl + Mysqlbarries30 Mar
    • Re: Perl + Mysqlbarries30 Mar
  • Perl + MysqlMichael Widenius31 Mar
  • Re: Perl + MysqlDana Prescott Kennedy Powers2 Apr
    • Re: Perl + MysqlMichael Widenius2 Apr
  • Re: Perl + MysqlRussell E Glaue9 Apr
    • Re: Perl + MysqlDana Prescott Kennedy Powers10 Apr
      • Re: Perl + MysqlCristian Giussani10 Apr
      • Re: Perl + MysqlRussell E Glaue10 Apr
        • Re: Perl + MysqlDana Prescott Kennedy Powers10 Apr
  • Re: Perl + MysqlRussell E Glaue20 Jun
    • Re: Perl + MysqlDana Powers21 Jun
      • Re: Perl + Mysqlbarries22 Jun
        • Re: Perl + MysqlRussell E Glaue22 Jun
          • Re: Perl + Mysqlbarries22 Jun
            • Re: Perl + MysqlSasha Pachev23 Jun
              • MySQL SNMPRussell E Glaue23 Jun
                • Re: MySQL SNMPSasha Pachev24 Jun
        • Re: Perl + MysqlDana Powers27 Aug
    • Re: Perl + MysqlSinisa Milivojevic22 Jun