﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Ayende Rahien commented on RavenDB Lazy Requests</title><description>Alex,
Two different use cases, as AsLazy wouldn't work, the Lazily has to be the last thing happening on the query</description><link>http://ayende.com/63491/ravendb-lazy-requests#comment19</link><guid>http://ayende.com/63491/ravendb-lazy-requests#comment19</guid><pubDate>Sun, 21 Aug 2011 07:51:05 GMT</pubDate></item><item><title>Ayende Rahien commented on RavenDB Lazy Requests</title><description>Walter,
The problem is that we tried, and it turns out that there aren't any queries that we can do this on using our architecture.
It would requires us to do pull things together that are currently separated.
You can look at what Raccoon Blog is doing to see how this works</description><link>http://ayende.com/63491/ravendb-lazy-requests#comment18</link><guid>http://ayende.com/63491/ravendb-lazy-requests#comment18</guid><pubDate>Sun, 21 Aug 2011 07:50:15 GMT</pubDate></item><item><title>Ayende Rahien commented on RavenDB Lazy Requests</title><description>Frans,
That ignores caching and parallel IO, though</description><link>http://ayende.com/63491/ravendb-lazy-requests#comment17</link><guid>http://ayende.com/63491/ravendb-lazy-requests#comment17</guid><pubDate>Sun, 21 Aug 2011 07:48:47 GMT</pubDate></item><item><title>Alex K commented on RavenDB Lazy Requests</title><description>I should read comments before I post. So instead, I'll make feature request for the blog to delete and edit the comments.</description><link>http://ayende.com/63491/ravendb-lazy-requests#comment16</link><guid>http://ayende.com/63491/ravendb-lazy-requests#comment16</guid><pubDate>Sat, 20 Aug 2011 20:28:42 GMT</pubDate></item><item><title>Alex K commented on RavenDB Lazy Requests</title><description>I'm curious about why the two different techniques were chosen for the two scenarios in the examples given. Is it a technical limitation (inordinate difficulty of implementing Lazily for Load, maybe?) that prevents the .Lazily() from being the one API to rule them all? Would've aligned it better with PLINQ's .AsParallel(), AsOrdered(), etc. usage.</description><link>http://ayende.com/63491/ravendb-lazy-requests#comment15</link><guid>http://ayende.com/63491/ravendb-lazy-requests#comment15</guid><pubDate>Sat, 20 Aug 2011 20:25:50 GMT</pubDate></item><item><title>Walter Poch commented on RavenDB Lazy Requests</title><description>Will you implement this on the Blog? I want to check how the profiler looks like after this =)

Congrats!</description><link>http://ayende.com/63491/ravendb-lazy-requests#comment14</link><guid>http://ayende.com/63491/ravendb-lazy-requests#comment14</guid><pubDate>Sat, 20 Aug 2011 18:02:36 GMT</pubDate></item><item><title>Frans Bouma commented on RavenDB Lazy Requests</title><description>Executing queries in parallel on the server... That might actually be slower than executing them in sequence, due to I/O. If, say, 4 queries are executed in parallel and they touch data in multiple places on disk, it will take the HDD several step actions to fulfill the parallel queries, as it has to step back and forth. This is slow. doing the queries in sequence actually might be faster, as the HDD then doesn't have to step that often. </description><link>http://ayende.com/63491/ravendb-lazy-requests#comment13</link><guid>http://ayende.com/63491/ravendb-lazy-requests#comment13</guid><pubDate>Sat, 20 Aug 2011 09:43:33 GMT</pubDate></item><item><title>Ayende Rahien commented on RavenDB Lazy Requests</title><description>Kurke,
There are only 2 - 3 things that actually need this, and trying to implement the API that you have in mind would be freakishly complex and very brittle</description><link>http://ayende.com/63491/ravendb-lazy-requests#comment10</link><guid>http://ayende.com/63491/ravendb-lazy-requests#comment10</guid><pubDate>Sat, 20 Aug 2011 01:32:21 GMT</pubDate></item><item><title>Ayende Rahien commented on RavenDB Lazy Requests</title><description>Njy,
You can't mix read / write requests, that is not an issue</description><link>http://ayende.com/63491/ravendb-lazy-requests#comment9</link><guid>http://ayende.com/63491/ravendb-lazy-requests#comment9</guid><pubDate>Sat, 20 Aug 2011 01:31:40 GMT</pubDate></item><item><title>Ayende Rahien commented on RavenDB Lazy Requests</title><description>Simon,
Yes, the typo is only in the post, and has been fixed</description><link>http://ayende.com/63491/ravendb-lazy-requests#comment8</link><guid>http://ayende.com/63491/ravendb-lazy-requests#comment8</guid><pubDate>Sat, 20 Aug 2011 01:30:26 GMT</pubDate></item><item><title>Nabil commented on RavenDB Lazy Requests</title><description>Agree with tobi.
Don't really like the fluent Lazily in session.Advanced.Lazily.Load&lt;User&gt;("users/ayende").
Would prefer consistently using Lazily() extension method throughout. </description><link>http://ayende.com/63491/ravendb-lazy-requests#comment7</link><guid>http://ayende.com/63491/ravendb-lazy-requests#comment7</guid><pubDate>Fri, 19 Aug 2011 21:57:02 GMT</pubDate></item><item><title>tobi commented on RavenDB Lazy Requests</title><description>I detest the fluent naming style very much. It does not even help with reading. Reminds me of the early attempts to make managers able to read code 30 years ago by using natural language syntax. Never works, never helps. Just goes against existing naming conventions.</description><link>http://ayende.com/63491/ravendb-lazy-requests#comment6</link><guid>http://ayende.com/63491/ravendb-lazy-requests#comment6</guid><pubDate>Fri, 19 Aug 2011 14:54:29 GMT</pubDate></item><item><title>Daniel Lidström commented on RavenDB Lazy Requests</title><description>Perhaps you should trademark that last statement: It Just Works :-) Oh, maybe it's taken already, oh well :-)</description><link>http://ayende.com/63491/ravendb-lazy-requests#comment5</link><guid>http://ayende.com/63491/ravendb-lazy-requests#comment5</guid><pubDate>Fri, 19 Aug 2011 13:19:03 GMT</pubDate></item><item><title>Kurke commented on RavenDB Lazy Requests</title><description>A question about the API - You have the .Lazily part.
This means you have to duplicate your API to support each action, lazily (returns Lazy&lt;T&gt; instead of T...). 

What do you think about the following?
var lazyUser = session.Advanced.Lazily(x =&gt; x.Load&lt;User&gt;("users/ayende"));
Where here Lazily is a simple extension method that returns Lazy&lt;T&gt;.

(I am a young programmer, I really don't know which option to prefer :)...)
</description><link>http://ayende.com/63491/ravendb-lazy-requests#comment3</link><guid>http://ayende.com/63491/ravendb-lazy-requests#comment3</guid><pubDate>Fri, 19 Aug 2011 11:47:41 GMT</pubDate></item><item><title>njy commented on RavenDB Lazy Requests</title><description>There is a way from the client to enable/disable the parallel execution of batched lazy requests? I'm thinking about a classic "insert doc" -&gt; "get latst 5 doc" flow: i would be able to use the lazy evaluation, eventually, but i also would like to mantain the order of the single requests.

Waddaya think, am i missing something?</description><link>http://ayende.com/63491/ravendb-lazy-requests#comment2</link><guid>http://ayende.com/63491/ravendb-lazy-requests#comment2</guid><pubDate>Fri, 19 Aug 2011 10:56:17 GMT</pubDate></item><item><title>Simon Bartlett commented on RavenDB Lazy Requests</title><description>I hope .Laziliy() is only spelt incorrectly in this code sample? ;)</description><link>http://ayende.com/63491/ravendb-lazy-requests#comment1</link><guid>http://ayende.com/63491/ravendb-lazy-requests#comment1</guid><pubDate>Fri, 19 Aug 2011 10:02:52 GMT</pubDate></item></channel></rss>