A now, B later

[Donald McLean]

Hi all,

This is a pattern/design question.

I have a piece of code, it turns out that after I complete part A, I have to give up the thread and wait for something else to happen before I can come back and complete part B. This is the first time I've had this kind of thing in a program, but I expect to see more of it.

I wrote something using a Lift Actor that works, but I was wondering if there were any documented patterns for this kind of thing.

Thanks,

Donald

[Matt Farmer]

Can the thing you're waiting on for Part B send a message to your Actor?

—
Matt Farmer | Blog | Twitter

GPG: CD57 2E26 F60C 0A61 E6D8  FC72 4493 8917 D667 4D07

--
--
Lift, the simply functional web framework: http://liftweb.net
Code: http://github.com/lift
Discussion: http://groups.google.com/group/liftweb
Stuck? Help us help you: https://www.assembla.com/wiki/show/liftweb/Posting_example_code

---
You received this message because you are subscribed to the Google Groups "Lift" group.
To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Matt Farmer]

Oh sorry. Didn't read your message closely enough.  Lol. 

Yeah I usually use actors. Check out this repo I've been working on. If you feel dissatisfied with how it's working. Mu examples are in Akka but the same patterns work with lift. 

https://github.com/farmdawgnation/actor-patterns

—
Matt Farmer | Blog | Twitter

GPG: CD57 2E26 F60C 0A61 E6D8  FC72 4493 8917 D667 4D07

[Brett Grace]

In addition to Matt's list of actor patterns (thank you), the Finite State Machine is a common pattern in actor systems:

http://erlang.org/documentation/doc-4.8.2/doc/design_principles/fsm.html
http://doc.akka.io/docs/akka/snapshot/scala/fsm.html

If you only have two phases it's probably overkill.