On Thu, 15 Feb 2007, Jan Wieck wrote: > On 2/15/2007 2:25 PM, Vivek Khera wrote: >> On Feb 15, 2007, at 8:28 AM, [EMAIL PROTECTED] wrote: >> >>> It seems to me that your "interactive slonc" will need to have a >>> LOT of >>> internal mechanism in order to work. You would need to fairly much >>> define >>> a full-scale language with variables, operators for "string >>> smashing," and >>> such like. There are two directions that can take you: >> >> This is the purpose for which tcl was invented, more or less... I'm >> sure Jan would love that :-) > > That'd lead in the end to SlonEM, the Slon Enterprise Manager. A > graphical utility that you use to drag'n'drop your configuration > together, right click to view status and details and so on ;-) > > > Jan
I'm not sure if you meant that in jest or are serious but you raise a good point. There are sets of needs for a Slony configuration tool. There are times when you want to be able to build scripts to automatically configure/alter Slony configurations where you often want to deal with conditionals, looping and error handling in some automated fashion. Then there is the need for a easy to use configuration and monitoring utility that people can use to get Slony clusters running. I am not sure these should be the same tool. Right now Slonik is both a command line processor/front end but also does more than that (ie execute script, lock set...). We might want to break slonik into two pieces. An API that contains any of the required set setup, locking logic etc. This API could be used by multiple admin front ends (slonik, pgadmin, SlonEM..). And a command line processor that provides a similar interface as slonik currently provides. I don't think this would be that hard to divide slonik in this fashion the code is mostly divided like that anyway. Writing a Perl module wrapper that exposes the API shouldn't be that difficult either (I suspect the same could be done for tcl). Would that make the altperl tools easier to maintain? Steve Singer > > -- > #======================================================================# > # It's easier to get forgiveness for being wrong than for being right. # > # Let's break this rule - forgive me. # > #================================================== [EMAIL PROTECTED] # > _______________________________________________ > Slony1-general mailing list > [email protected] > http://gborg.postgresql.org/mailman/listinfo/slony1-general > _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
