Comments on: Lessons learned from getting .NET to REST with Java http://blog.dynatrace.com/2009/08/24/lessons-learned-from-getting-net-to-rest-with-java/ dynaTrace Blog on Performance, Scalabilty and Architecture - Java and .NET Application Performance Management Thu, 02 Sep 2010 08:57:48 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Andreas Grabner http://blog.dynatrace.com/2009/08/24/lessons-learned-from-getting-net-to-rest-with-java/comment-page-1/#comment-5903 Andreas Grabner Thu, 27 Aug 2009 13:07:00 +0000 http://blog.dynatrace.com/?p=699#comment-5903 Hi Tbee You are correct - browser are doing it this way and the HttpWebRequest would do it the same way. In my case - my .NET Client established a separate connection each time when accessing the service. So each time I had two roundtrips - and - in case it was a POST request with a big HTTP body I also had twice the network load I also posted this blog on theserverside.com - there I got some nice recommendations about using a HEAD request first - then doing the actual request once knowing what kind of authentication is required Hi Tbee
You are correct – browser are doing it this way and the HttpWebRequest would do it the same way. In my case – my .NET Client established a separate connection each time when accessing the service. So each time I had two roundtrips – and – in case it was a POST request with a big HTTP body I also had twice the network load

I also posted this blog on theserverside.com – there I got some nice recommendations about using a HEAD request first – then doing the actual request once knowing what kind of authentication is required

]]> By: Tbee http://blog.dynatrace.com/2009/08/24/lessons-learned-from-getting-net-to-rest-with-java/comment-page-1/#comment-5902 Tbee Thu, 27 Aug 2009 12:56:04 +0000 http://blog.dynatrace.com/?p=699#comment-5902 After the initial BASIC authentication, browsers send the authorization header with each and every request. In effect; after loggin in, each request holds the encoded password. Lousy from a security perspective. So if you do a REST, follow by a BASIC authentication, the next request should immediately include that header. After the initial BASIC authentication, browsers send the authorization header with each and every request. In effect; after loggin in, each request holds the encoded password. Lousy from a security perspective.

So if you do a REST, follow by a BASIC authentication, the next request should immediately include that header.

]]> By: Twitter Trackbacks for Lessons learned from getting .NET to REST with Java Performance, Scalability and Architecture – Java and .NET [dynatrace.com] on Topsy.com http://blog.dynatrace.com/2009/08/24/lessons-learned-from-getting-net-to-rest-with-java/comment-page-1/#comment-5881 Twitter Trackbacks for Lessons learned from getting .NET to REST with Java Performance, Scalability and Architecture – Java and .NET [dynatrace.com] on Topsy.com Tue, 25 Aug 2009 17:34:41 +0000 http://blog.dynatrace.com/?p=699#comment-5881 [...] Lessons learned from getting .NET to REST with Java Performance, Scalability and Architecture – Ja... blog.dynatrace.com/2009/08/24/lessons-learned-from-getting-net-to-rest-with-java – view page – cached #Performance, Scalability and Architecture – Java and .NET Application Performance Management (dynaTrace Blog) RSS Feed Performance, Scalability and Architecture - Java and .NET Application Performance Management (dynaTrace Blog) » Lessons learned from getting .NET to REST with Java Comments Feed Performance, Scalability and Architecture - Java and .NET Application Performance Management (dynaTrace Blog) ASP.NET GridView Performance Java Memory Problems — From the page [...] [...] Lessons learned from getting .NET to REST with Java Performance, Scalability and Architecture – Ja… blog.dynatrace.com/2009/08/24/lessons-learned-from-getting-net-to-rest-with-java – view page – cached #Performance, Scalability and Architecture – Java and .NET Application Performance Management (dynaTrace Blog) RSS Feed Performance, Scalability and Architecture – Java and .NET Application Performance Management (dynaTrace Blog) » Lessons learned from getting .NET to REST with Java Comments Feed Performance, Scalability and Architecture – Java and .NET Application Performance Management (dynaTrace Blog) ASP.NET GridView Performance Java Memory Problems — From the page [...]

]]> By: Andreas Grabner http://blog.dynatrace.com/2009/08/24/lessons-learned-from-getting-net-to-rest-with-java/comment-page-1/#comment-5877 Andreas Grabner Tue, 25 Aug 2009 12:15:58 +0000 http://blog.dynatrace.com/?p=699#comment-5877 @Mike: Thanks for the hint. I double checked - but the 2nd roundtrip was actually a POST @Mark: seems you are working with the stonehenge project. Check out the work I did with Stonehenge in the following blog - http://blog.dynatrace.com/2009/06/15/tracing-problems-in-project-stonehenge-and-other-heterogeneous-systems/ @Mike: Thanks for the hint. I double checked – but the 2nd roundtrip was actually a POST

@Mark: seems you are working with the stonehenge project. Check out the work I did with Stonehenge in the following blog – http://blog.dynatrace.com/2009/06/15/tracing-problems-in-project-stonehenge-and-other-heterogeneous-systems/

]]> By: Lessons learned from getting .NET to REST with Java « Jasper Blog http://blog.dynatrace.com/2009/08/24/lessons-learned-from-getting-net-to-rest-with-java/comment-page-1/#comment-5872 Lessons learned from getting .NET to REST with Java « Jasper Blog Tue, 25 Aug 2009 06:52:56 +0000 http://blog.dynatrace.com/?p=699#comment-5872 [...] Read more: dynaTrace [...] [...] Read more: dynaTrace [...]

]]> By: Dial Up Can Not Compare To UK Broadband Internet | Intro to Business BroadBand http://blog.dynatrace.com/2009/08/24/lessons-learned-from-getting-net-to-rest-with-java/comment-page-1/#comment-5870 Dial Up Can Not Compare To UK Broadband Internet | Intro to Business BroadBand Tue, 25 Aug 2009 01:20:57 +0000 http://blog.dynatrace.com/?p=699#comment-5870 [...] Lessons learned from getting .NET to REST with Java Performance … [...] [...] Lessons learned from getting .NET to REST with Java Performance … [...]

]]> By: Mark http://blog.dynatrace.com/2009/08/24/lessons-learned-from-getting-net-to-rest-with-java/comment-page-1/#comment-5866 Mark Mon, 24 Aug 2009 22:59:12 +0000 http://blog.dynatrace.com/?p=699#comment-5866 http://incubator.apache.org/stonehenge/ http://incubator.apache.org/stonehenge/

]]> By: Mike http://blog.dynatrace.com/2009/08/24/lessons-learned-from-getting-net-to-rest-with-java/comment-page-1/#comment-5865 Mike Mon, 24 Aug 2009 20:20:08 +0000 http://blog.dynatrace.com/?p=699#comment-5865 In "Calling via HTTP POST", double-check the second POST is actually a POST. .Net has the same weird behavior as IE when it encounters a Not-Authorized on a resource. It will retry the request with the right header, but often with a GET and not POST. I've run into this several times. In “Calling via HTTP POST”, double-check the second POST is actually a POST. .Net has the same weird behavior as IE when it encounters a Not-Authorized on a resource.

It will retry the request with the right header, but often with a GET and not POST. I’ve run into this several times.

]]> By: DotNetShoutout http://blog.dynatrace.com/2009/08/24/lessons-learned-from-getting-net-to-rest-with-java/comment-page-1/#comment-5862 DotNetShoutout Mon, 24 Aug 2009 16:52:31 +0000 http://blog.dynatrace.com/?p=699#comment-5862 <strong>Lessons learned from getting .NET to REST with Java Performance, Scalability and Architecture – Java and .NET Application Performance Management (dynaTrace Blog)...</strong> Thank you for submitting this cool story - Trackback from DotNetShoutout... Lessons learned from getting .NET to REST with Java Performance, Scalability and Architecture – Java and .NET Application Performance Management (dynaTrace Blog)…

Thank you for submitting this cool story – Trackback from DotNetShoutout…

]]>