I don't think your getting dozens of dependencies from atmosphere. If you have a maven build...atmosphere just has two GWT dependencies you need to specify, with all transitive dependencies its about 7-8 jars but you could exclude container specific jars if you wanted.
Also you don't need to use maven to use atmosphere...you can add them manually if you prefer. -Dave On Thursday, November 15, 2012 9:42:02 AM UTC-7, Magnus wrote: > > Hi, > > I want my server to send events to clients. > > It is very important to me to minimize the changes to my project, i. e. > the best case would be a jar file and some classes, not a large framework > with a lot of other functionality I do not need. > > I spent some time now trying to get atmosphere work within my environment, > but I am not so happy withit: dozens of atmosphere-*.jar files, the need to > use maven to get it running, and other things. > > Now I came across Tomcat's comet support: > One jar file (catalina.jar) and a few classes (CometProcessor, ...). > > It would be fine if I can use it for my purposes. > > Question: > Are there serious drawbacks when using this solution? > Where can I find a minimal example? > > Thanks! > > Magnus > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/2noWd6yvEVMJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
