https://github.com/fmpwizard/liftnamedcomet

Some helper classes/traits to easy the use of named comet actors
https://github.com/fmpwizard/liftnamedcomet

Last synced: 21 days ago
JSON representation

Some helper classes/traits to easy the use of named comet actors

• Host: GitHub
• URL: https://github.com/fmpwizard/liftnamedcomet
• Owner: fmpwizard
• Created: 2011-08-31T08:10:39.000Z (over 13 years ago)
• Default Branch: master
• Last Pushed: 2013-05-13T01:38:39.000Z (over 11 years ago)
• Last Synced: 2024-04-16T06:22:03.237Z (8 months ago)
• Language: Scala
• Homepage:
• Size: 995 KB
• Stars: 7
• Watchers: 2
• Forks: 2
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
## Update

This library/module was integrated into Lift core on version 2.5. I hope to write an upgrade doc soon, but in the meantime, 

the file names you'll need to use are:

```

NamedCometActorSnippet.scala  //have your snippet (the ones that adds the comet to the page) extend this

NamedCometActorTrait.scala //have your comet class extend this

NamedCometListener.scala //this is the singleton with useful methods to get the list of comet actors

```

Thanks

This project is a library that aims at making the use of

named comet actors in Lift a little easier.

Usage:

=====

On your lift project you can add the dependency as:

    resolvers ++= Seq("snapshots" at "http://oss.sonatype.org/content/repositories/snapshots",

                    "releases"  at "http://oss.sonatype.org/content/repositories/releases")

    libraryDependencies ++= Seq("com.fmpwizard" %% "lift-named-comet" % "0.3")

For a sample project using this library visit:

[Lift Auction](https://github.com/fmpwizard/lift_auction)

Documentation:

=============

You can read this blog post to which describes how to use it::

[fmpwizard's blog](http://blog.fmpwizard.com/lift-comet-actor-per-tab-library)

Features:

=========

* You can have a CometActor of the same class, but different instances of it on different tabs.

* Only the CometActor that is going to update the Ui is going to get a message.

* You can send messages to a CometActor from other sessions (including stateless RESTful end points.

* When a CometActor has not been present on a page after a defined lifespan, it is removed from the central registry.

* Hides the whole implementation so the user can focus on the CometActor functionality. 

Enjoy

  Diego