Atlas 2: HTTP POST is slower and it's default in Atlas

Atlas by default makes HTTP POST for all AJAX calls. Http POST is more expensive than Http GET. It transmits more bytes over the wire, thus taking precious network time and it also makes ASP.NET do extra processing on the server end. So, you should use Http Get as much as possible. However, Http Get does not allow you to pass objects as parameters. You can pass numeric, string and date only. When you make a Http Get call, Atlas builds an encoded url and makes a hit to that url. So, you must not pass too much content which makes the url become larger than 2048 chars. As far as I know, that's what is the max length of any url.

Another evil thing about http post is, it's actually 2 calls. First browser sends the http post headers and server replies with "HTTP 100 Continue". When browser receives this, it sends the actual body. Here's what the headers look like:

Request:

POST / Atlas1 / Default . aspx HTTP / 1.1 __serviceMethodName = Timeout&__serviceMethodParams = {}&__VIEWSTATE =/ wEPDwUJMTY3NTY1MjM2ZGSlWDXIdYj44hhTUd0z8yyp1q %2 bUtw %3 d %3 d Response: HTTP / 1.1 100 Continue Server: ASP . NET Development Server / 8.0 . 0.0 Date : Mon , 11 Sep 2006 15 : 04 : 13 GMT Content-Length: 0

After getting this clearance from the server, the actual body is sent. This is done in order to prevent long posts which are not going to succeed anyway if the server cannot accept it. But it comes at the cost of network latency.

So, Http Get should be at least twice faster than Http Post.

Here's how you make Http GET calls in Atlas:

Step 1: Decorate web method with attribute

First you need to put a special attribute on the web method:

[WebMethod] [WebOperation( true )] public string HelloWorld() { return " Hello World " ; }

Step 2: Set useGetMethod=true while making the call

Here's how you call the web method using Http Get:

WebService.HelloWorld( { useGetMethod: true , onMethodComplete: function (result) { debug.dump(result); } } );

Note: It needs to be a web service (.asmx). It will not work if you use it on page methods.

Please see this page in Atlas Quickstart for further info.

Published Friday, September 22, 2006 7:11 PM by omar
Filed under:

Comments

# MVP Award

Friday, November 03, 2006 11:59 PM by Omar AL Zabir (MVP)

I have been awarded MVP Award 2007 on Visual C# again. This is my second year. This time the gifts are...

# ATLAS: POST slower than GET

Monday, November 13, 2006 9:53 AM by DotNetKicks.com

You've been kicked (a good thing) - Trackback from DotNetKicks.com

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Monday, November 13, 2006 10:25 AM by Michael Yeaney

This behavior has to be due to the server-side implementation of the Atlas libraries.  The HTTP response code 100 (continue) is not 'required' simply because of a post (per HTTP RCF) - some server's choose to return this, some don't (usually due to code / configuration).  

Here's a simple test:  Whip up your own AJAX implementation using one of the many XmlHttpRequest patterns out there, and hook up an HTTP sniffer (preferably on a box WITHOUT the Atlas extensions).  The calls are quick and concise - 1 POST, 1 response (hopefully a 200!!!).

Simpler test:  Hook up a standard POST form to a server without the Atlas extensions - still no double hit.

I can reproduce these results on any machine I have available, and all the big libraries out there give the same results (Prototype, BackBase, etc.) yield the same results.

HTH,

Mike

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Tuesday, November 14, 2006 10:17 AM by Zen

Can you elaborate more on this statement:

"However, Http Get does not allow you to pass objects as parameters. You can pass numeric, string and date only."

Thanks!

Zen

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Sunday, November 19, 2006 1:01 AM by RussianGeek

Can you help me here: http://forums.asp.net/1470075/ShowThread.aspx ?

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Tuesday, November 28, 2006 3:33 AM by Michael Schwarz

Hi, the http 100 status code will only give the client an indenticator that the server is ready to retreive big data. Not every post will return an http 100.

Next you can submit the same data using GET like you can do with an POST request, there is no difference.

The difference between POST and GET:

- POST will not be cachable in browser or proxy

- GET has a maximum length of X bytes (where X depends on the web browser and the number of fields you want to send)

Michael

http://www.ajaxpro.info/

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Tuesday, November 28, 2006 5:37 AM by Omar AL Zabir

I did a HTTP POST and here's the output from ieHTTPHeaders plug-in:

--------------------

POST /CoreServices.asmx?mn=SavePage HTTP/1.1

Accept: */*

Accept-Language: en-gb,en-us;q=0.5

Referer: http://www.pageflakes.com/

Content-Type: application/json

Accept-Encoding: gzip, deflate

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; FDM; InfoPath.2; .NET CLR 3.0.04324.17)

Host: www.pageflakes.com

Content-Length: 102

Connection: Keep-Alive

Cache-Control: no-cache

{"pageData":{"id":????,"index":6,"title":"Test","columnCount":3,"columnSizes":["33%","33%","33%"]}}

*** HTTP/1.1 100 Continue ***

*** HTTP/1.1 200 OK ***

Cache-Control: private, max-age=0

Date: Sun, 19 Nov 2006 07:46:56 GMT

Content-Type: application/json; charset=utf-8

Server: Microsoft-IIS/6.0

X-Powered-By: ASP.NET

X-AspNet-Version: 2.0.50727

Content-Encoding: gzip

Vary: Accept-Encoding

Transfer-Encoding: chunked

-----------------

You see, there are two response. First HTTP/1.1 100 Continue and Second one is the HTTP/1.1 200 OK

From W3C.org HTTP specification, here's what I found:

http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html

--------------------

8.2.3 Use of the 100 (Continue) Status

The purpose of the 100 (Continue) status (see section 10.1.1) is to allow a client that is sending a request message with a request body to determine if the origin server is willing to accept the request (based on the request headers) before the client sends the request body. In some cases, it might either be inappropriate or highly inefficient for the client to send the body if the server will reject the message without looking at the body.

Requirements for HTTP/1.1 clients:

- If a client will wait for a 100 (Continue) response before

sending the request body, it MUST send an Expect request-header

field (section 14.20) with the "100-continue" expectation.

- A client MUST NOT send an Expect request-header field (section

14.20) with the "100-continue" expectation if it does not intend

to send a request body.

Because of the presence of older implementations, the protocol allows ambiguous situations in which a client may send "Expect: 100- continue" without receiving either a 417 (Expectation Failed) status or a 100 (Continue) status. Therefore, when a client sends this header field to an origin server (possibly via a proxy) from which it has never seen a 100 (Continue) status, the client SHOULD NOT wait for an indefinite period before sending the request body.

Requirements for HTTP/1.1 origin servers:

- Upon receiving a request which includes an Expect request-header

field with the "100-continue" expectation, an origin server MUST

either respond with 100 (Continue) status and continue to read

from the input stream, or respond with a final status code. The

origin server MUST NOT wait for the request body before sending

the 100 (Continue) response. If it responds with a final status

code, it MAY close the transport connection or it MAY continue

to read and discard the rest of the request. It MUST NOT

perform the requested method if it returns a final status code.

- An origin server SHOULD NOT send a 100 (Continue) response if

the request message does not include an Expect request-header

field with the "100-continue" expectation, and MUST NOT send a

100 (Continue) response if such a request comes from an HTTP/1.0

(or earlier) client. There is an exception to this rule: for

compatibility with RFC 2068, a server MAY send a 100 (Continue)

status in response to an HTTP/1.1 PUT or POST request that does

not include an Expect request-header field with the "100-

continue" expectation. This exception, the purpose of which is

to minimize any client processing delays associated with an

undeclared wait for 100 (Continue) status, applies only to

HTTP/1.1 requests, and not to requests with any other HTTP-

version value.

- An origin server MAY omit a 100 (Continue) response if it has

already received some or all of the request body for the

corresponding request.

- An origin server that sends a 100 (Continue) response MUST

ultimately send a final status code, once the request body is

received and processed, unless it terminates the transport

connection prematurely.

- If an origin server receives a request that does not include an

Expect request-header field with the "100-continue" expectation,

the request includes a request body, and the server responds

with a final status code before reading the entire request body

from the transport connection, then the server SHOULD NOT close

the transport connection until it has read the entire request,

or until the client closes the connection. Otherwise, the client

might not reliably receive the response message. However, this

requirement is not be construed as preventing a server from

defending itself against denial-of-service attacks, or from

badly broken client implementations.

Requirements for HTTP/1.1 proxies:

- If a proxy receives a request that includes an Expect request-

header field with the "100-continue" expectation, and the proxy

either knows that the next-hop server complies with HTTP/1.1 or

higher, or does not know the HTTP version of the next-hop

server, it MUST forward the request, including the Expect header

field.

- If the proxy knows that the version of the next-hop server is

HTTP/1.0 or lower, it MUST NOT forward the request, and it MUST

respond with a 417 (Expectation Failed) status.

- Proxies SHOULD maintain a cache recording the HTTP version

numbers received from recently-referenced next-hop servers.

- A proxy MUST NOT forward a 100 (Continue) response if the

request message was received from an HTTP/1.0 (or earlier)

client and did not include an Expect request-header field with

the "100-continue" expectation. This requirement overrides the

general rule for forwarding of 1xx responses (see section 10.1).

--------------------

So, I assume may be my Proxy is doing that HTTP 100 or may be IIS 6 is sending HTTP 100 always.

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Monday, December 11, 2006 8:21 AM by Austin Lazanowski

May i use your article on my new Microsoft supporting weblog/forum/discussion/news site? Alot of my visitors will be interested in using the asp.net framework as well as the atlas.net framework. Of course the "read more" will continue towards your site. Let me know, thanks.

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Saturday, May 05, 2007 4:40 PM by Buch

<link>rx-24h.com/.../link>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Tuesday, May 22, 2007 11:23 AM by Miltiades

Interesting...

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Tuesday, May 22, 2007 9:04 PM by nsz7yt7wb1

yybw0ylfcyl [URL=www.572133.com/485067.html] 76sewf6rupqjs2psg [/URL] 6aawzukcbajw

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Wednesday, May 23, 2007 12:11 AM by Lefteris

interesting

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Wednesday, May 23, 2007 2:06 AM by Vangelis

Interesting...

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Wednesday, May 23, 2007 9:35 AM by Fotis

Interesting...

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Thursday, May 24, 2007 6:06 PM by Jazdomah

Interesting...

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Thursday, May 24, 2007 9:10 PM by Gdsffsd

<a href="extremedrawing.tripod.com/">adult comics</a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Thursday, May 24, 2007 9:26 PM by Gdsffsd

<a href="extremedrawing.tripod.com/">adult comics</a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Tuesday, June 05, 2007 7:44 PM by Ignatios

interesting

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Wednesday, June 06, 2007 2:47 PM by Kleanthe

interesting

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Saturday, June 09, 2007 9:30 AM by Anaklets

interesting

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Saturday, June 09, 2007 11:25 AM by Polyvios

Interesting...

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Sunday, June 10, 2007 12:35 AM by Constantine

Interesting...

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Sunday, June 24, 2007 12:47 AM by Augustinos

Interesting...

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Sunday, June 24, 2007 11:27 PM by Xenophon

Interesting...

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Tuesday, June 26, 2007 12:37 AM by Lazaros

interesting

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Tuesday, June 26, 2007 3:10 PM by Evripides

interesting

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Sunday, July 15, 2007 5:39 AM by Aiolos

interesting

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Monday, July 16, 2007 6:27 PM by Spyridon

interesting

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Wednesday, July 18, 2007 7:58 AM by Myron

Interesting...

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Wednesday, July 18, 2007 10:20 PM by Leo

Interesting...

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Thursday, July 19, 2007 2:54 PM by Sebastianos

interesting

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Friday, July 20, 2007 9:36 AM by chris24ali

INTERESTING

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Wednesday, July 25, 2007 12:20 PM by Pericles

interesting

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Thursday, July 26, 2007 11:41 PM by Robert

Managed Hosting, Colocation and Data Center Services by victoryushchenkonashpresudent ...

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Friday, July 27, 2007 2:49 PM by Kristion

interesting

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Saturday, July 28, 2007 8:26 PM by Prokopios

interesting

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Saturday, July 28, 2007 9:31 PM by Paulos

Interesting...

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Sunday, July 29, 2007 2:09 AM by Ambrosios

Interesting...

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Tuesday, July 31, 2007 8:22 AM by Timotheos

interesting

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Wednesday, August 01, 2007 8:11 AM by Athanasios

Interesting...

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Wednesday, August 01, 2007 11:14 PM by Aniketos

interesting

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Tuesday, August 07, 2007 12:17 PM by very cheap airline tickets

Good site!

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Saturday, September 01, 2007 11:21 AM by bang

cheap ticket cheapticketbla.blogspot.com cheap ticket

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Saturday, September 15, 2007 10:45 AM by bob

somestrangetextvista http://peace.com

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Saturday, September 15, 2007 10:46 AM by bob

somestrangetextvista http://peace.com

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Friday, September 21, 2007 10:00 PM by replica watches

replica watches <a href=" www.bloglines.com/.../watchesreplica ">replica watches</a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Tuesday, October 02, 2007 5:40 PM by jtgjNbTHjVGgVXyEvnl

VnLFTk 360dfv923bf

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Thursday, October 04, 2007 8:28 PM by Marki

Learn flintknapping techniques of Paleo-Americans and later Woodland styles of making arrowheads, knives, and spearpoints in this workshop for beginners and intermediates. The materials fee is included in cost of class and will cover instructional videos and all the tools and materials for making arrowheads, knives and spear points.

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Wednesday, October 31, 2007 2:21 PM by bang

qTVPR0 hi nice site thank you http://peace.com

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Thursday, November 01, 2007 6:14 PM by x5ma3y

Hi! Good Site! Keep Doing That!

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Thursday, November 01, 2007 8:09 PM by gfdg787

Nice site. Thank you.

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Thursday, November 01, 2007 9:33 PM by 1k34tt32

Thank you for the informative work!

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Thursday, November 01, 2007 10:47 PM by 1k34tt32

Very good site. Thanks!!!

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Friday, November 02, 2007 12:02 AM by cv435t661

Very good site. Thanks!!!

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Friday, November 02, 2007 12:20 AM by zeip6bnt5

Hi! Good Site! Keep Doing That!

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Friday, November 02, 2007 1:37 AM by gfdg787

Hi! Good Site! Keep Doing That!

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Friday, November 02, 2007 2:59 AM by cv435t661

Very good site. Thanks!!!

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Friday, November 02, 2007 4:30 AM by gfdg787

Very good site. Thanks!!!

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Friday, November 02, 2007 4:31 AM by x5ma3y

Thank you, looking forward to many more visits!

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Friday, November 02, 2007 5:49 AM by x5ma3y

Thank you for the informative work!

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Friday, November 02, 2007 7:17 AM by zeip6bnt5

Nice site. Thank you.

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Friday, November 02, 2007 9:06 AM by swbyu652

Nice site. Thank you.

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Monday, November 05, 2007 9:54 AM by 8j84n

<a href=" users1.nofeehost.com/.../ebony.html ">ebony</a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Monday, November 05, 2007 11:25 AM by gfdg787

<a href=" users1.nofeehost.com/.../adult-sites.html ">adult sites</a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Monday, November 05, 2007 2:31 PM by sdf2361

<a href=" users1.nofeehost.com/.../adult-video.html ">adult video</a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Tuesday, November 06, 2007 4:18 AM by cv435t661

<a href=" users1.nofeehost.com/.../cfnm.html ">cfnm</a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Tuesday, November 06, 2007 5:22 AM by 12yr46s

<a href=" users1.nofeehost.com/.../adult-personals.html ">adult personals</a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Wednesday, November 07, 2007 12:39 AM by sdf2361

<a href=" users1.nofeehost.com/.../adult-finder.html ">adult finder</a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Monday, December 24, 2007 3:41 PM by hipnoj

<a href= http://index1.alkortas.com >citric acid combined with potassium hydroxide</a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Tuesday, December 25, 2007 4:54 PM by hipnoj

<a href=  ></a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Wednesday, December 26, 2007 12:01 AM by hipnoj

<a href=  ></a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Wednesday, December 26, 2007 12:01 AM by hipnoj

<a href=  ></a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Wednesday, December 26, 2007 7:17 AM by hipnoj

<a href=  ></a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Wednesday, December 26, 2007 1:21 PM by hipnoj

<a href=  ></a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Wednesday, December 26, 2007 7:03 PM by hipnoj

<a href=  ></a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Thursday, December 27, 2007 1:28 AM by hipnoj

<a href=  ></a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Thursday, December 27, 2007 8:08 AM by hipnoj

<a href=  ></a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Thursday, December 27, 2007 1:56 PM by hipnoj

<a href=  ></a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Thursday, December 27, 2007 7:42 PM by hipnoj

<a href=  ></a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Friday, December 28, 2007 2:17 AM by hipnoj

<a href=  ></a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Friday, December 28, 2007 8:09 PM by hipnoj

<a href= http://index1.doulbe.com >black *** cocksuckers</a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Saturday, December 29, 2007 11:13 AM by hipnoj

<a href= http://index1.rixota.com >stow and pass</a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Sunday, December 30, 2007 3:28 PM by hipnoj

<a href= http://index1.doulbesite.com >smoothing looping movie clips in flash 8</a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Tuesday, January 01, 2008 6:43 PM by hipnoj

<a href= http://index1.npols.com >honeysuckle candy sticks</a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Thursday, January 03, 2008 5:32 AM by hipnoj

<a href= http://index1.blackrom.com >gangbang in public</a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Thursday, January 03, 2008 5:32 AM by hipnoj

<a href= http://index1.blackrom.com >gangbang in public</a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Saturday, January 05, 2008 8:43 AM by hipnoj

<a href= http://index1.aptintro.com >sexivideo</a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Saturday, January 05, 2008 3:03 PM by hipnoj

<a href= http://index1.jintrosite.com >personal assistant in las vegas</a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Saturday, January 05, 2008 10:05 PM by hipnoj

<a href= http://index1.thejintro.com >strap on</a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Saturday, January 05, 2008 10:05 PM by hipnoj

<a href= http://index1.thejintro.com >strap on</a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Sunday, January 06, 2008 5:14 AM by hipnoj

<a href= http://index1.yourwertool.com >exprantnet deltapassport</a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Sunday, January 06, 2008 8:26 PM by hipnoj

<a href= http://index1.thewertool.com >fieldcrest farm</a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Sunday, January 06, 2008 8:26 PM by hipnoj

<a href= http://index1.thewertool.com >fieldcrest farm</a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Sunday, January 06, 2008 8:26 PM by hipnoj

<a href= http://index1.thewertool.com >fieldcrest farm</a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Sunday, January 06, 2008 8:26 PM by hipnoj

<a href= http://index1.thewertool.com >fieldcrest farm</a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Monday, January 07, 2008 4:02 AM by hipnoj

<a href= http://index1.lopwersite.com >ma.medical association</a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Tuesday, January 08, 2008 5:11 AM by hipnoj

<a href= http://index1.elurker.com >combining ceramics fused glass</a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Tuesday, January 08, 2008 4:22 PM by hipnoj

<a href= http://index1.themounter.com >sample resumes for human resource assistant</a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Tuesday, January 15, 2008 5:24 PM by hipnoj

<a href= http://index1.realken.com >female sexual dysfunktional</a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Wednesday, January 16, 2008 12:02 AM by hipnoj

<a href= http://index1.openelk.com >campgroundi</a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Wednesday, January 16, 2008 7:18 AM by hipnoj

<a href= http://index1.lkhub.com >tugjobgirls</a>

# re: Atlas 2: HTTP POST is slower and it's default in Atlas

Wednesday, January 16, 2008 4:29 PM by hipnoj

<a href= http://index1.lkewat.com >westies movie</a>

Leave a Comment