Hi!
I'm doing a webservice that can be stop using a request, I had followed one
forum here. But I run in a trouble stopping the component in a virtual host set
up.
Here is the first testcase 1, I can stop the server using
http://localhost:8182/stop
///
// testcase 1//
Hi Thierry,
Thanks for the reply, i got it working on stopping without our
Application. But when I add the code for our Application, it seems it can't
fully exit the jvm. I tried it first without
loadBalance.attach(/webservice/PEITCache, new
Hello,
it seems that non-daemon threads are still running.
Could you check using the jstack utility
(http://java.sun.com/j2se/1.5.0/docs/tooldocs/share/jstack.html)?
You may have to shutdown the cache in your MainPEITCacheApplication#stop
method (something like ccm.shutdown()).
Best regards,
Hi Thierry,
I had modify MainPEITCacheApplication to override the stop but
still not stopping
/
MainPEITCacheApplication
/
public class MainPEITCacheApplication
Hi Gerald,
as you seem to use an auxiliary cache could you try something like
RemoteCacheServerFactory.shutdownImpl( , Registry.REGISTRY_PORT )
before the shutdown of the cache manager?
Or specify directly the host and port of the remote cache server.
Bast regards,
Thierry Boileau
Hi,
I'm using restlet with google app engine. I need to support session state. If a
user logs in, I want to remember that they're still logged in when they switch
between pages, so they don't have to keep re-authenticating.
I read through the posts here about sessions not being supported by
Hi dj,
session are strictly forbidden in REST, because the scalability advantage of
restful applications will get lost, because caches wont work. For details see
the dissertation of Roy Fielding, the founder of the REST architecture style,
espacially chapter 5
Hi Thierry,
Got it working now, it with the CompositeCacheManager, I just need to
clean up everything.
Thanks
public class MainPEITCacheApplication extends Application {
Hello,
as said Stephan, servlets sessions are not supported.
If a user logs in, I want to remember that they're
still logged in when they switch between pages, so they
don't have to keep re-authenticating.
There is no magic. If you have a look at each request issued from the browser,
you will
Hey Stephen,
Ok so I get that sessions shouldn't be supported by rest, totally fine with
that. I'm confused about how to use basic auth then instead, if that's the
preferred method.
If we use basic auth, then we need to send the username and password as plain
text, right? This could be fixed
Dj,
I'm glad you asked this. I've really lucked out so far and have always worked
in an environment that uses client certificates for authentication. The
identity of the user is established on every single connection, and I never
have to worry about it. But in the near future, I'm going to
I have been away from Restlets for a long time... far too long.
I was just looking at the API for the Restlet extensions - I can't find
OAuth library (org.restlet.ext.oauth) there. Is that what the bug below is
talking about (documentation missing beside the JavaDocs)?
Thanks for clearing this
12 matches
Mail list logo