Tapestry 5
  1. Tapestry 5
  2. TAP5-634

Google App Engine Support: ability to disable code that creates new threads

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.1.0.3
    • Fix Version/s: 5.1.0.3
    • Component/s: tapestry-core, tapestry-ioc
    • Labels:
      None

      Description

      Right off the bat, the restriction in GAE that no threads be created will affect a few, small sections of Tapestry.

      In the larger scheme of things, a tapestry-googleappengine library may require a few things:

      • Make the GAE services (such as UserService) injectable
      • Support for JDO (much like tapestry-hibernate, today)
      • Other, unforseen

      Also, depending on the license of GAE (and availabilty through Maven) may need to host such a library at Tapestry360.

        Activity

        Howard M. Lewis Ship made changes -
        Status Open [ 1 ] Closed [ 6 ]
        Fix Version/s 5.1.0.3 [ 12313782 ]
        Resolution Fixed [ 1 ]
        Howard M. Lewis Ship made changes -
        Summary Google App Engine Support: disable code that creates new threads Google App Engine Support: ability to disable code that creates new threads
        Description Right off the bat, the restriction in GAE that no threads be created will affect a few, small sections of Tapestry.

        In the larger scheme of things, a tapestry-googleappengine library may require a few things:
        - Make the GAA services (such as UserService) injectable
        - Support for JDO (much like tapestry-hibernate, today)
        - Other, unforseen

        Also, depending on the license of GAE (and availabilty through Maven) may need to host such a library at Tapestry360.
        Right off the bat, the restriction in GAE that no threads be created will affect a few, small sections of Tapestry.

        In the larger scheme of things, a tapestry-googleappengine library may require a few things:
        - Make the GAE services (such as UserService) injectable
        - Support for JDO (much like tapestry-hibernate, today)
        - Other, unforseen

        Also, depending on the license of GAE (and availabilty through Maven) may need to host such a library at Tapestry360.
        Howard M. Lewis Ship made changes -
        Description Right off the bat, the restriction in GAA that no threads be created will affect a few, small sections of Tapestry.

        In the larger scheme of things, a tapestry-googleappengine library may require a few things:
        - Make the GAA services (such as UserService) injectable
        - Support for JDO (much like tapestry-hibernate, today)
        - Other, unforseen

        Also, depending on the license of GAA (and availabilty through Maven) may need to host such a library at Tapestry360.
        Right off the bat, the restriction in GAE that no threads be created will affect a few, small sections of Tapestry.

        In the larger scheme of things, a tapestry-googleappengine library may require a few things:
        - Make the GAA services (such as UserService) injectable
        - Support for JDO (much like tapestry-hibernate, today)
        - Other, unforseen

        Also, depending on the license of GAE (and availabilty through Maven) may need to host such a library at Tapestry360.
        Howard M. Lewis Ship made changes -
        Field Original Value New Value
        Assignee Howard M. Lewis Ship [ hlship ]
        Howard M. Lewis Ship created issue -

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Howard M. Lewis Ship
          • Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development