Just wondering, are you developing a completely new framework based on new concepts, or are you abstracting a layer over existing frameworks with existing concepts?
I'd have to go with both, and neither. :) See below. In your diagrams they seem to imply that it is an asynchronous request-reply, but in your code examples they imply a synchronous call. This pattern would be highly synchronous. I think any asynchronisation would have to reside external to the Request object, unless you can think of a way? Have you found faults with existing frameworks such as Qt (QCoreApplication) or Twisted? These frameworks achieve the same results where you can dispatch an async call, and have a result returned to you similar to a callback. Quite the contrary. :) I've found many uses for concepts within Qt, some of which I'd love to use outside of Qt as well, hence the implementation into a more widely accessible object. I'm more interested in the actual concepts than I am in particular implementations like the ones listed above. I have no doubts the Request Pattern already exists. The reason for me defining it is to find out more about it as it has become quite useful in my code. Could you point me to where Twisted does this? Thanks Justin. On 17 April 2014 00:06, Justin Israel <[email protected]> wrote: > Just wondering, are you developing a completely new framework based on new > concepts, or are you abstracting a layer over existing frameworks with > existing concepts? > > In your diagrams they seem to imply that it is an asynchronous > request-reply, but in your code examples they imply a synchronous call. > Have you found faults with existing frameworks such as Qt > (QCoreApplication) or Twisted? These frameworks achieve the same results > where you can dispatch an async call, and have a result returned to you > similar to a callback. > > > > > On Thu, Apr 17, 2014 at 9:07 AM, Marcus Ottosson > <[email protected]>wrote: > >> Hey guys, >> >> I'm looking for feedback on a programming pattern I've been tinkering >> with lately; its a simplification of signalling an event and getting a >> result back via another signal, such as when a GUI requests an event to be >> performed, but the event it performed elsewhere - most likely a separate >> object - and gets an event back from the separate object upon completion. >> >> The Request Pattern <http://rfc.abstractfactory.io/spec/45/> >> >> Let me know what you think. >> >> Best, >> Marcus >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Python Programming for Autodesk Maya" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/python_inside_maya/022c3632-4637-4cc5-bd37-8fe1a4a91127%40googlegroups.com<https://groups.google.com/d/msgid/python_inside_maya/022c3632-4637-4cc5-bd37-8fe1a4a91127%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "Python Programming for Autodesk Maya" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/python_inside_maya/CAPGFgA2x2DcD%2BH20eN95-WqbzErLFKAsrBueYvyy1F1tzsx71A%40mail.gmail.com<https://groups.google.com/d/msgid/python_inside_maya/CAPGFgA2x2DcD%2BH20eN95-WqbzErLFKAsrBueYvyy1F1tzsx71A%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- *Marcus Ottosson* [email protected] -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/CAFRtmOBHvHKHMQy5WXrgr028U-erhF%3DGwgMq09cGZ5mPOZgsRA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
