Webtide

Category: Uncategorized

  • Open source Closed Project

    This is a repost of an old old blog entry that has become relevant again.

    I was hoping to make my next entry one of a technical nature, but the
    JBoss™ Group have just asked me to remove the JBoss™ image from the Jetty pages!

    The JBoss™ image used has been contributed to the Open Source project and is
    available
    on sourceforge     plus variations of it are distributed with JBoss releases.
    For several years, it has been used on the
    Jetty home page
    and also on the
    Jetty Powered page.
    Both link through to the JBoss™ project page on sourceforge.

    Jetty is the default web tier of JBoss releases
    from 3.0 to 3.2.1 and continues to be the web container of choice for many JBoss users.
    While I no longer work with JBoss™ Group LLC, I am still very much supportive of the JBoss™
    the OS project and continue to maintain the Jetty integration sar (as I am also supportive of
    Jetty in Geronimo, JOnAS, Avalon, etc…).

    I don’t expect JBoss™ Group LLC to hand out my new business cards for me, but I
    do expect an open source project to be administered on a non-discriminatory basis.
    Unfortunately the administration of JBoss is falling way short of that:

    • My name and photo have been removed from the list of

      current and retired JBoss™ contributors      . OK, so I’m still in the source and CVS log but
      an open source project should not take commercial alliances into consideration when
      deciding how much credit to give for contributions. At least the
      Wayback Machine remembers
      me.
    • I have been censored out of the jboss-user and jboss-dev mailing lists, even when
      my posts are bug reports or answers to user questions. I have posted 2 training
      announcements to jboss-user, which I believe is appropriate usage for a list provided
      by sourceforge whose moderators
      frequently allow
      such announcements from a
      particular contributor. I certainly have not been trolling the jboss mailing lists
      like JBoss Group employees

      have trolled
      the Jetty lists.
    • Now it is not OK for an open source project to graphically link to
      another open source project because of trademarcs held by an
      individual
      and
      licensed to a particular service provider.

    I guess JBoss™ Group LLC have answered
    Rickards question
    on the server side on the use of trademarcs to control an open source project.

    I believe the jetty project has the moral and legal right to use that image. It is
    an open source image of a trademarc that has not been enforced, linking to
    a project that Jetty made significant contributions to and includes a fork of
    the Jetty code.

    But rights aside, I do not want to go against the wishes of a copyright holder.
    So I have removed the image from the Mort Bay pages and will start the process of
    removing them from the next Jetty releases and thus from the jetty pages.

    I have also responded to JBoss™ Group asking if Jetty could license the trademarc and
    asking what are the not-for-profit non-discriminatory licensing terms. So far the only
    response has been along the lines of: just take down the images or we will get legal on
    your arse. This is not good enough and I believe JBoss™ Group LLC owe the community
    a fair and open policy for the use of the name and image that they have contributed
    to. Something like a LinuxMark would be great.

    JBoss and JBoss Group are a registered trademark and servicemark of
    Marc Fleury
    under operation by The JBoss Group, LLC. All similarity between the terms free speech and
    free beer is purely coincidental. No copyrights have been harmed in the writing of this blog. Individual
    outrage may vary.

  • Project Oort – a cometd cluster

    Cometd Oort is extension to the jetty/java cometd server intended to provide a scalable comet cluster. Cometd Seti is an extension of Oort to enable the identification and location of connected users within an Oort cluster and the routing of messages to specific users.

    The jetty/java cometd server is itself highly scalable and can terminate 10s of thousands of cometd loads. However clusters are desirable for for many deployments either more simultaneous clients are required, message rates may limit the clients that can be supported per server or availability targets are such that multiple servers are required.

    The services that Oort provides include:

    • The discovery and connection of other Oort Comet servers.
    • The distribution of channels

    Once a cluster is established, use

  • Lazy Cometd Messages

    Lazy Messages

  • Jetty and OSGI at Eclipse

    The last several months have brought a lot oof hangs with the jetty OSGI bits and piecesa of things at eclipse. We have finally standardized the way we distribute our binaries within our various p2 repositories. We have a honest to goodness WTP adaptor for jetty that people can use. We have contributed to both Helios and indigo and have had at least one of our other bundles picked up and contributed to another project (the junit pde testing bundle)
    First a bit about how we are distributing the bundles. Underneath the normal download location of http://download.eclipse.org/jetty we have the updates directory which has jetty-bundles-7.x and jetty-wtp underneath which are composite p2repositories. This location will be the standard place to consume our eclipse signed bundles from. There will be a jetty-bundles-8.x location once we iron out the source locations of the jsp-2.2 dependencies in jetty8. Underneath these top level composite p2repositories we have a development directory which is populated from the hudson.eclipse.org buld server. For the WTP bundles the development repository is being populated with each build. We do this in part so we are certain that our bundles are successfully making it through the whole eclipse signing and packing process. Since the velocity of change in these bundles are not extreme it seems minor to be doing the signing and packing process like is. The benefit is that once tested the development directory can be renamed into a proper version and added into the composite metadata.