GWT and .net server side (JSON)

251 views
Skip to first unread message

roundcrisis

unread,
Jul 5, 2009, 7:40:12 AM7/5/09
to Google Web Toolkit
Hi there

I was wondering if there are any recommendations regarding working
with a .net server side.

My idea on how to work with this scenario is to communicate with the
GWT widgets via JSON and use my views as host pages so there is no
problem with same origin principle.

This seems to work, however its very time consuming, as , if you want
to do any changes, you need to compile and that takes about two
minutes.

As an alternative approach I thought I would create a proxy to
redirect my server requests, so I can use my server side JSON in
hosted mode, ... is this something that would be recommended?

or any other simpler alternatives?


Thanks

sqtz

unread,
Jul 5, 2009, 8:42:40 AM7/5/09
to Google Web Toolkit
Hi,

I'm working with .net server side and gwt on the client.

i use Jayrock JSON-RPC implementation on server side.

On the client i use my own JSON-RPC implementation coded in GWT.

I use GWT Javascript Overlays too.

i do not use any asp.net page. Only a minimal host aspx page and
the .net form authentication framework to do the login.

my application has many modules this way.

sorry my english.

Roundcrisis

unread,
Jul 5, 2009, 8:46:34 AM7/5/09
to Google-We...@googlegroups.com
Hi Eduardo:

Thanks for the info, I ll check out JSON-RPC by JayRock + JSON-RPC
Cheers

Andrea

Thomas Broyer

unread,
Jul 5, 2009, 10:07:02 AM7/5/09
to Google Web Toolkit


On 5 juil, 13:40, roundcrisis <roundcri...@gmail.com> wrote:
> Hi there
>
> I was wondering if there are any recommendations regarding working
> with a .net server side.
>
> My idea on how to work with this scenario is to communicate with the
> GWT widgets via JSON and use my views as host pages so there is no
> problem with same origin principle.
>
> This seems to work, however its very time consuming, as , if you want
> to do any changes, you need to compile and that takes about two
> minutes.

You don't need to recompile each time you make a change to your GWT
code; just use the -noserver mode:
http://code.google.com/webtoolkit/doc/1.6/FAQ_DebuggingAndCompiling.html#How_do_I_use_my_own_server_in_hosted_mode_instead_of_GWT's
The only drawback is that you don't see the changes to your CSS (if it
lives in your GWT project) and generated resources (such as
ImageBundles) unless you re-deploy the stylesheet, because everything
is served from your own server. It also means you cannot test your
code on external browsers (compile/browse is completely useless in -
noserver mode, unless you're actually compiling directly into your
server's directory)

> As an alternative approach I thought I would create a proxy to
> redirect my server requests, so I can use my server side JSON in
> hosted mode, ... is this something that would be recommended?

That's what we're using for more than a year (when we cross -
noserver's limitations boundaries) and it works like a charm. I
attached our proxy servlet to issue 3131
http://code.google.com/p/google-web-toolkit/issues/detail?id=3131

Reply all
Reply to author
Forward
0 new messages