Mail sent on the 09/10 and apparently lost.
---
Hello Duong,
what kind of problem are you experiencing with the creation of directories?
best regards,
Thierry Boileau
I don't mean to throw a wet blanket on the GWT discussion, but my
(limited) impression of GWT was that it was trying to
On Thu, 2008-09-11 at 12:04 +0200, Thierry Boileau wrote:
Mail sent on the 09/10 and apparently lost.
---
Hello Duong,
what kind of problem are you experiencing with the creation of directories?
best regards,
Thierry Boileau
Wow, thank you Thierry.
(1) I will find time to try
Fantastic, Thierry. Thanks much.
Dumb question: how, or should, one integrate the notion of allow
post/allow put, etc, in the TestServer code?
Mark
On Sep 11, 2008, at 3:03 AM, Thierry Boileau wrote:
Mail sent on the 09/02 and apparently lost.
---
Hello Mark,
it may be too late, but I
Hi Mark,
the TestServer is a very simple server-side application using only a
Restlet.
In this case, if you want to handle only, let's say, GET requests, you
have to test it by yourself and generate correctly the response in the
handle(request, Response) method.
I suggest you develop the
In a real application, it is usually better to write high-level Resources
than Restlets, though wiring in a Restlet as in the Foo.zip example is often
the briefest way to return an HTTP response. Have a look at this tutorial,
if you haven't already:
Hi Duong,
1) No, the sample code is not based on GWT-RPC API. The server side is
based on Restlet and I simply answer to requests (in this case AJAX
requests) with a simple line of plain text (it could be XML)
2) Let me think about it! :)
Best regards,
Thierry Boileau
--
Restlet ~ Core
Thanks for this, Thierry!
I have changed some names, made some more objects (a Component, Application,
and Resource ...) and wrapped it up into an Eclipse project with Ant build
script, hosted mode launcher, and a working server side, added tomcat's
web.xml, embedded the Restlet jars, and made
Thank you. In fact, that example made it to hardcopy and accompanied
me to lunch twice this week. Good stuff.
Mark
On Sep 11, 2008, at 10:06 AM, Rob Heittman wrote:
In a real application, it is usually better to write high-level
Resources than Restlets, though wiring in a Restlet as in
Does someone have a single snippet of code that shows how the Restlet-
GWT API would work with the GWT tutorial w/RPC in StockWatcher?
Pseudo code would be fine.
http://code.google.com/docreader/#p=google-web-toolkit-
doc-1-5s=google-web-toolkit-doc-1-5t=GettingStartedRPC
That is, what
I don't mean to throw a wet blanket on the GWT discussion, but my
(limited) impression of GWT was that it was trying to abstract away
the web, rather than embrace it. Rather than dealing with loosely
coupled services, resources, and representations, it wraps everything
into a nice tidy Java API
GWT and Restlet is a *very* different paradigm from GWT-RPC. There is no
creation of RPC interfaces, no Async or Service constructs. That is, as
Justin said, an abstraction that largely pretends the Web isn't there,
instead of leveraging its capabilities. This is why GWT-RPC is not a
feature of
Restlet's GWT (Server) Extension, being just a wrapper around ServerServlet
that can also pass calls to the GWT Hosted Mode adapter, is one small class
file that has been in 1.1 milestone builds for almost a year now. My
company uses it in a number of large production and in-development
Hi Mark, I've been working on a longish example (Chesstlet) that pulls
together a number of Restlet and GWT techniques, but this won't be ready
until November, due to some commitments I have in early October that
complicate my availability. In the meantime, maybe the best thing to do
would be to
Thank you for the kind and speedy response, Rob.
I intend to spend the week, and then some, on this subject, and would
be happy to receive any guidance or code you can muster. In return, I
can post my newcomer questions and results.
I'm curious: how is it that the hosted mode Restlet GWT
14 matches
Mail list logo
