by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • May 23 2017 14:09

    jeremydmiller on dotnet

    Bumping to 0.2.13 (compare)

  • May 23 2017 14:07

    jeremydmiller on dotnet

    Add global.json file, bump stor… (compare)

  • May 23 2017 14:07
    jeremydmiller closed #12
  • Apr 27 2017 20:40
    joemcbride synchronize #12
  • Apr 27 2017 20:03
    joemcbride edited #12
  • Apr 27 2017 20:02
    joemcbride opened #12
  • Feb 03 2017 17:14

    CoreyKaylor on dotnet

    Added license (compare)

  • Nov 23 2016 14:01

    jeremydmiller on dotnet

    trying to harden the Queue disp… (compare)

  • Nov 08 2016 14:02

    jeremydmiller on dotnet

    tweaks to the logging, added In… (compare)

  • Sep 23 2016 16:34

    CoreyKaylor on dotnet

    Bumping version and LightningDB… (compare)

  • Sep 22 2016 23:06

    CoreyKaylor on dotnet

    Timeout slow clients (compare)

  • Sep 22 2016 22:01

    CoreyKaylor on dotnet

    Fixes for sending retries, adde… Hardening the sending error pol… (compare)

  • Sep 02 2016 18:54

    CoreyKaylor on dotnet

    Bumping version on lmdb storage (compare)

  • Sep 02 2016 18:48

    CoreyKaylor on dotnet

    Updated lmdb lib for bug fixes (compare)

  • Aug 29 2016 20:34

    CoreyKaylor on dotnet

    Updated LightningDB, fixed test… (compare)

  • Aug 20 2016 15:36

    CoreyKaylor on dotnet

    Bumping version (compare)

  • Aug 20 2016 15:31

    CoreyKaylor on dotnet

    Fixed incorrect logic on length… (compare)

  • Aug 20 2016 00:03

    CoreyKaylor on dotnet

    Bumping version (compare)

  • Aug 20 2016 00:02

    CoreyKaylor on dotnet

    More polish and some end-to-end… (compare)

  • Aug 15 2016 23:39

    CoreyKaylor on dotnet

    Added GetMessage for diagnostic… Bumping version (compare)

Corey Kaylor
@CoreyKaylor
You can opt for no storage and it will just flow through the Rx stream without persistence.
Or rather it will be a stub persistence that does nothing.
Christos Matskas
@cmatskas
Ah great. Since the queue on my end is only used to process incoming messages, I can totally bypass this.. thanks
i'll dig more through the code today and I'll try to get a PoC tonight...thanks for your time and effort and for the cool #oss
Corey Kaylor
@CoreyKaylor
The storage is there more for durability and recovery. Can get at least once delivery by doing persistence, but obviously has a cost.
so the queue mechanics are a store and forward message delivery, not a broker or server if that makes sense
similar to msmq for the most part
Christos Matskas
@cmatskas
Yes, it does
and I don't need the server part anyway as it's implemented elsewhere
Hopefully I won't need to bother you with any more questions :) - but.... just be on the lookout
Corey Kaylor
@CoreyKaylor
I’m usually around :)
Christos Matskas
@cmatskas
cool :)
I'm off but thanks again for your help
Corey Kaylor
@CoreyKaylor
you’re welcome
bryancrosby
@bryancrosby
Any tutorials available for this yet?
Jeremy D. Miller
@jeremydmiller
@CoreyKaylor As a way for me to get a lot deeper into the LQ codebase before I do the memory-only transport option, want me to do this?
Corey Kaylor
@CoreyKaylor
If you’re game @jeremydmiller I’m fine with that.
Jeremy D. Miller
@jeremydmiller
G
Jeff Doolittle
@jeffdoolittle
@CoreyKaylor are there docs anywhere for LightningQueues? or is the answer "check out the tests"
Jeremy D. Miller
@jeremydmiller
Check out the tests and/or look at the usage within the FubuMVC codebase
Corey Kaylor
@CoreyKaylor
@jeffdoolittle been out of band for a bit w/regard to new company efforts but winding down now. Sorry for not responding earlier. FubuMVC.LightningQueues is probably the most comprehensive use-case. But honestly if you just take a look at the Queue class. It’s pretty simple to follow and understand. The Rx-ified approach makes it pretty easy on the eyes from a complexity standpoint IMO.
Jeff Doolittle
@jeffdoolittle
awesome thanks for replying. so far I'm just playing around with it but long term I may be looking to replace our reliance on MassTransit so I'm trying to put the pieces together.
Corey Kaylor
@CoreyKaylor
Depending on your existing abstractions, it could work just fine. The big piece that the library puts on you to decide is routing.
On you, or on the service bus library that takes it on as a dependency.
That’s where fubu came in. Along with error policies on message retries, etc.
Jeff Doolittle
@jeffdoolittle
yeah, I am looking forward to seeing what jeremy has in mind for this in 2017
I'm guessing that's what this is a placeholder for: https://github.com/JasperFx/jasper
Corey Kaylor
@CoreyKaylor
it is, it’s always been a moving target though as to what would make it in
the bus portion is the only sure thing to my knowledge
Brad Barnich
@BradBarnich
Hi, is there a license for LQ?
Corey Kaylor
@CoreyKaylor
Should be MIT, but realize now that you’ve asked that it’s not included in the repo.
Corey Kaylor
@CoreyKaylor
@BradBarnich I’ve added the license to the repository now.
Weston
@ronnyek
is lmdbmessage store not part of the nuget package?
also is there a snippet somewhere of like simplest example
I'm trying to convert test code over (which understandably is built for reuse and to be a bit abstract on purpose)
Weston
@ronnyek
ahh another package required for the lmdb store
Weston
@ronnyek
I am seeing this
Exception thrown: 'System.NullReferenceException' in LightningQueues.Storage.LMDB.dll
Exception thrown: 'System.NullReferenceException' in System.Private.CoreLib.dll
but its not actually breaking... is there any easy way to get more information about why publishing causes breakage?
Weston
@ronnyek
So I would like to use lightning queues as a sort of persistent job queue... I effectively send, to localhsot with appropriate port, then when I lose connectivity, I'm disposing the receiver, and then when connection comes back, I re-instantiate the receiver
is that the right way to handle things?
Jeremy D. Miller
@jeremydmiller
Sounds reasonable to me
Weston
@ronnyek
I noticed when I am calling send, and there is no receiver, its throwing extended network exception or something
it does seem to resume sending once my receiver re-attaches
Jeremy D. Miller
@jeremydmiller
C
orrect
Weston
@ronnyek
I guess my question there is, is the throwing of the exception normal, and if I am always intending to deal with this locally (even in process) do I have to go out via tcp?
Jeremy D. Miller
@jeremydmiller
So that’s all that LQ can do today. I did basically rewrite LQ directly into Jasper, and there we’re planning on also supporting HTTP for sending/receiving messages
Weston
@ronnyek
seems like it can use a lot of ports quickly
if you are rapidly pushing messages through it