Hi, Hélia --
Jerome's first guess was on target; per RFC 2616 section 8.1.4, clients
should by default be configured to allow no more than 2 concurrent
connections to the same host. I know for-sure that the default in Apache
HttpClient is this; examine the source of
Hello,
You need to encode your URL because the space are not valid character for a
URL. (space needs to become %20), I think their is an existing helper class
that can help you in the restlety API or check jakarta commons-net.
Regards,
Loïc
From:
Hi Rob
Thank you for this detailed answer. I've just read the part of the RFC
you mentionned : A single-user client SHOULD NOT maintain more than 2
connections with any server or proxy. I did not know that.
I have just tried to set a different number using an Apache HttpClient
and the methods
Loic,
As you can see in my second snippet, I used Reference.encode helper class to
encode the url (which use URLEncoder), but it seems that the Reference does
not recognize the encoded path as an absolute path, as described in the
exception.
Regards
Stephane
On Tue, Jun 3, 2008 at 11:09 AM,
Hello,
You must add the File client -- do this around the same time you add the
HTTP server:
+ comp.getClients().add(Protocol.FILE);
You can take this out:
- getConnectorService().getClientProtocols().add(Protocol.FILE);
Hi,
I am trying to wrap a custom Restlet application in a Servlet to facilitate
its deployment in a WAR file. The application needs to be initialized with
some parameters using the standard web.xml file.
My understanding is that it is possible to do it in 2 ways: Subclassing
ServletServer or
If you haven't already, you could check the diagnosis by just creating a new
Client object within each of your resources that is doing the recursive
calling. While this might be wasteful, it should at least rule out some
other cause of the trouble. Approximately how many recursions are you
Thank you Rob, you did it :).
Rob Heittman [EMAIL PROTECTED] wrote on 03/06/2008 16:35:58:
Hello,
You must add the File client -- do this around the same time you add
the HTTP server:
+ comp.getClients().add(Protocol.FILE);
You can take this out:
-
Sorry, to insist but I have tried all that (new Client object, etc.).
The maximum number of connection per host is the one I have set. This is
why I though the problem could maybe come from the server side.
Thx again for your help
Hélia
Rob Heittman a écrit :
If you haven't already, you
Hello Stephane,
it should work by doing so:
Directory directory = new Directory(getContext(),
LocalReference.createFileReference(C:\\Program
Files\\Apache Software Foundation\\Tomcat 5.5\\webapps\\mywebapp));
Best regards,
Thierry Boileau
Loic,
As you can see in my
I just set up a little test of the pattern and it runs fine, but of course
my server doesn't do any actual work. Is it possible that a blocking I/O
operation occurs in the ... part of your sample code?
On Tue, Jun 3, 2008 at 12:17 PM, Hélia Pouyllau
[EMAIL PROTECTED] wrote:
Sorry, to insist
Hi All,
I am a newbie to restlets. Currently I have a restlet client communicating
with the restlet engine on another machine. On the server side the code is
basically an Application extending *org.restlet.Application *which looks at
the URI and forward it to the correct resource.
I will like
It's quite horrible, but you can do casts like this:
HttpServletRequest awful = ((ServletCall)((HttpRequest)
request).getHttpCall()).getRequest();
This will, of course, break your application unless it is running in a very
specific Restlet configuration, and is probably inviting forward
Hey all,
We're noticing on 2-3 of our devs machines JVM crashes when trying to use
restlet, its happening often, but not consistently so I'm not sure whats
really triggering it, but its always in the same spot:
Instructions: (pc=0x0625ed3c)
0x0625ed2c: 5d dc 8b 03 53 8d 5e 34 ff 50 40 89 c7 8b
As the crash is *in* the VM code it would really help to know the specific
JVM version and the platform (OS, 32 vs 64 bit, etc) to reproduce it. I
have a pretty good laundry list of known issues on various VMs I can cross
check against.
We're noticing on 2-3 of our devs machines JVM crashes when
Enough workarounds exist that my company's been able to produce a full
WebDAV level 2 provider that runs on 1.0/1.1
Where can we find this source code?
Have you some pieces of code to show us how expose resource via WebDav
(MS Web Folders)?
Rob Heittman wrote:
I don't know if all the
The implementation I referred to in that particular February message was
work-for-hire for a proprietary customer.
But you might be able to find most of the relevant hints by looking at the
DAV 1 implementation with DAV 2 stubs in our GoGoEgo open source project,
gogoego.googlecode.com. We have
Hi Jerome,
Jerome Louvel wrote:
Hi Bruno,
I'm not sure we want to add such a feature in an official build.
Fair enough.
Also, if you can come up with a patch that would add a
getChallengeRequests():ListChallengeRequest method on Response and
deprecate the current challengeRequest
I tried it. I like it.
- R
I've just submitted a patch to
http://restlet.tigris.org/issues/show_bug.cgi?id=457
Basically, setChallengeRequest is deprecated (and uses the first entry in
the list) and replaced with addChallengeRequest and setChallengeRequests;
getChallengeRequest is also
Hi all, I just posted this article on Groovy and Restlet, and I
thought it might be of interest:
http://blog.arc90.com/2008/06/building_restful_web_apps_groovy_restlet_part_1.php
It's very, very basic, but the idea is that if there's interest, it'll
be a series, so it'll get more advanced. If
That's a new one on me, but Hardy has been the locus of a bunch of new JVM
crash issues, mainly with Athlon processors. Also there have been some
similar issues with 64-bit under Red Hat and Fedora.
This is the Sun JVM I get installing sun-java6-jdk from multiverse, and I
don't get JVM crashes on
21 matches
Mail list logo
