-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have a bunch of questions regarding several things. First group, I think I heard something about 0.9x being able to handle multiple installations from one queue daemon set, is there a guide for doing this? Also how would that affect memory usage for them? I also heard something about the memory usage going down in 0.9x from 0.8x, what is the current estimated usage?
Second group, I see you have opened up your sign-up for hosted versions, Do you have any capabilities in that for bring your own domain? I know I would like to be able to use a hosted version but I would want it as a subdomain of my domain. I have heard about Dreamhost's one click install and as a Dreamhost customer I am looking at that but I can not find anywhere if they run the daemons for those and I wondered if anyone here knew? Third group, I am trying to design a (mostly) free SMS sending service for use via an API that does not need the carrier to send messages. I tend to think of the requirement to enter the carrier as a weakness of statusnet and I was curious how hard it would be to implement a plugin to use such a service and remove the carrier question? I am especially worried about doing that myself as I do not have any OO based PHP experience, my PHP work has been done purely as procedural code. My understanding is this would cause an issue if I were to do a statusnet plugin. I was also curious about how different programmers feel about various API interface types, I was thinking that from a server standpoint with PHP that GET, POST, and COOKIE data are the easiest to use, but I do not know what kinds of data are easiest to send as a client using an API. My other similar question is about the response data format. For my own projects interfacing Flash ands PHP URL encoded variables were easiest, but that is only one type of client, what kinds of response formatting are easiest from an API callers perspective? Thanks, Glenn McGurrin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkuf7xUACgkQzSSLW0oTVN7BPACeJbZ7a0S+f+zgUrk5uFy6MWll qQoAnjyQmVNiiy7R5xwpIt/9n5MWTgS2 =bcdV -----END PGP SIGNATURE----- _______________________________________________ StatusNet-dev mailing list StatusNet-dev@lists.status.net http://lists.status.net/mailman/listinfo/statusnet-dev
