StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16047130
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-04-16T21:08:25.643
FavoriteCount
0
LastActivityDate
2013-04-17T09:24:47.840
LastEditDate
2013-04-17T09:24:47.840
LastEditorUserId
217959
OwnerUserId
217959
ParentId
16040000
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
<pre><code>import akka.dataflow._ import scala.concurrent._, ExecutionContext.Implicits._ // the following are for duration import scala.language.postfixOps import scala.concurrent.duration._ object FlowTestApp extends App { val f = flow { println("in flow") "Hello world!" } onComplete println Await.ready(f, 1 second) } </code></pre> If you're thinking about using Akka Dataflow as a non-blocking alternative to threads, here's my 2 cents: Some core language features (e.g. loops, try/finally) break in the delimited code blocks. I've been using it for some I/O and I'm happy with it, but I'd make sure to keep it under the hood. %99 of akka-dataflow is Scala's continuations plugin. The definition of <a href="https://github.com/akka/akka/blob/master/akka-dataflow/src/main/scala/akka/dataflow/package.scala#L31" rel="nofollow">flow()</a> (which boggles my mind) and the pimped Future#apply() are really all that's needed, and they're quite small. Scala's continuations plugin, however, is much more generic than the problem of non-blocking threads. For an alternative solution, keep track of <a href="https://github.com/scala/async" rel="nofollow">scala-async</a>, which has a much more specific approach (transforming your seemingly sequential code into <code>future { ... } flatMap { ... }</code> blocks) I tried it last week, and as of that time scala-async's code transformation still covered less than what is supported by akka-dataflow, but from looking at the commit log it seems to be gaining fast and will soon surpass it.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POFailed A akka dataflow sample
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USnadavwr
UserOwnerUserId
1. USnadavwr
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POFailed A akka dataflow sample
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.