Module submission guideline - configuration storage I am trying to finish and submit my first module project. It's a QA/tab launcher thing that is meant for multisites. Basically, I am using a few different methods to retrieve a list of sites that are part of the same multisite as the site that the module is enabled on. The piece I have a question about is a configuration page that saves a list, from that list, of "enabled" sites.

Here is my problem: I want a multisite-wide configuration, but I am concerned about how i'm doing it. I understand that the Domain Access module would provide more than enough functionality for cross-site database access and would probably be more up to the Drupal guidelines, but it's extremely overkill! Domain Access will scare off people that don't want to configure each settings.php file, etc. 

All I need, literally, is to save 2 non-associative arrays in a way that each multisite has access. My current setup saves them in the public files directory as 2 .csv files, and works as well as I know how to code it; as far as saving .csv's and retrieving the rows go, I think i'm doing it right. It doesn't really have performance issues tied to it because it truly is a lightweight piece; the only reason i'm doing it this way is for global access.

My question is: is this going to get flagged as non-conformant to the Drupal way because i'm not saving it in a table? I don't see anything in the guides specifically guiding me away from doing it that way... but it's just a guess that they won't like it.
My advice to you is to submit your sandbox to Drupal.org Project Applications, and see what people say.  Its fairly rare to get an outright rejection.  People will inspect your code, offer suggestions for improvement, etc.  Better to get started ASAP.

As for your specific issue:  I think the way you are going about it is not in accordance with The Drupal Way ™.  Your best bet would probably be to generate a PHP file, only allowing your module to access this sort of administrative control from the site in Default.