Thanks a lot for your ideas. I already thought of a thread regularly checking on updates. I will just think a bit more about pros and cons and then implement one of the mentioned possibilities.
Thanks again and best regards, Erik Am 12.06.2011 um 14:55 schrieb "Thiago H. de Paula Figueiredo" <thiag...@gmail.com>: > On Sun, 12 Jun 2011 08:22:17 -0300, Erik Fäßler <erik.faess...@uni-jena.de> > wrote: > >> Hey all, > > Hi! > >> the web application I'm developing depends on some resources which may >> change on a regular basis. I have a plain Java application which is >> responsible for creating/updating these resources, e.g. a database table. >> I would like this update application to be able to tell my tapestry web app >> that new data is available and should be loaded. I would like to send a >> command like "update" to the web app which then would tell the services that >> new resources are available and that they should reload these. >> The question: Which would be easiest way to do this? > > Just create a page and use the page activation context to receive the desired > command. > >> I have found a package "tapestry-resteasy" which seems to offer a RESTful >> interface quite nicely. However, I do not intend to offer a public API to my >> web application - I would rather hide the update functionality from the >> public. > > Any URL in a webapp is public, so you need to implement some kind of > authentication. > > Another option is to implement a service that opens a server socket to > receive the commands. Again, you'll need to implement some kind of > authentication. > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and > instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
