Re: Some questions

[Rich Bodo]

David,

        There is not much development going on in the GNUComm
        architecture at the moment.  GNUComm is a very ambitious,
        long-term project, that will be most practically useful in
        coordinating the development of several individually useful
        programmable servers.  The idea is that these servers, such as
        Bayonne, will be required to interoperate and, in some cases,
        share application code.  To help that happen, documentation,
        applications and libraries coordination will be developed in
        GNUComm.  We have a roadmap, but the only completed server
        that is in use at the moment is Bayonne.

        As far as choosing a gatekeeper.  I don't think H.323 will
        re-license, but that's not a problem.  We can still
        communicate with non-gnu software, we just can't link with
        it.  There are plenty of GPL'd SIP stacks out there, so they
        may be more helpful in the long term.  I'm more concerned at
        the moment with getting Bayonne apps developed, but scratch
        your own itch.  If you've got some ideas or some code, I'd be
        happy to put it in a contrib section.

        When I say I want to allow the user with low-end hardware an
        option, I am, of course, being practical.  If you take care in
        the design, it is possible to add support for say, voice
        modems, to an enterprise class application.

        Working with GNUe is a long-term goal, primarily to share
        application and data objects.

        As far as scalability and monitoring are concenred, that's
        what the various data buses are for in the architecture
        diagram.  Bayonne already has an experimental data-redundancy
        bus, and there has been some work done on the trip server.  We
        have to crawl before we can walk, though.

-Rich

Rich Bodo | address@hidden | 650-964-4678

On Tue, 15 Jan 2002, David wrote:

> I am trying to understand some more about gnucomm.
>
> I was wondering if I could ask some questions. I have read most of the
> information that I can find and would like to clarify a few things.
>
> Your http://www.gnu.org/software/gnucomm/overview.html document indicates
> that you will have a gatekeeper. Have you approached openH323 with respect to
> either re-licensing or even dual licensing their Open H323 software? Would
> this in fact help? I would have thought it would provide not only a basic
> protocol stack but a number of other associated programs covering both
> protocol monitoring and end point clients.
>
> On the topics of Service activation and service assurance does the GNUe
> initiative have applications or structures here that will be used or are you
> looking at something new? You mention that the configuration should be simply
> to the end user and that low end computing power should not be a barrier to
> entry but i was wondering how you were going to build scalability.
> Configuring new services and then monitoring one machine to see that it is
> performing correctly but what about 300 machines all with different versions
> of software and different prompts. Is there any planned mechanism to manage a
> very large and diverse network?
>
> I trust these questions are not bothersome but I am somewhat looking for
> answers. I checked out the source tree but I am not a programmer so I was
> looking for documentation of which I didn't find alot and wasn't able to
> understand the source tree all that well.
>
> Thankyou for any help you can give me.
>
> Best Regards,
>
> David Price
>
> _______________________________________________
> Help-gnucomm mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/help-gnucomm
>