axum support

[icepuma]

Hey,
love the work you did so far for atrium.
Do you plan on adding axum support for the xrpc-server or what are your plans with this crate?

Best regards
icepuma

[sugyan]

Thank you very much.
I was recently working on getting firehose to work. I needed to support the subscription feature, so I looked at the atproto repository and found a package called xrpc-server that handles message streams, so I mimicked that.
I didn't think much about using axum, etc. to make pds work at this point, but if the ATrium project is to "implement AT Protocol in Rust," then of course it should be done, and if there is demand for it, I will give priority to it.

Is this an answer to your question?

[icepuma]

I could in fact have a look at the support, make a PR and we discuss it there or am I in the middle of you doing huge overhauls inside the code base?

[sugyan]

Hmmm, I have not yet established a clear policy on what to do.
I suppose I could move xrpc-server elsewhere and replace it with something entirely new, I'm not doing anything special at this time.
Would it be better to make ATrium an organization and separate each repository, and within that, create the xrpc-server crate from scratch with you as the author?

[icepuma]

Having a crates workspace doesn't hurt, because you need all the classes in one space and a monorepo approach is cool enough imho.
You could provide multiple "server backends" via feature switches like one called "axum", one called "actix", ...
And with the beauty of code generation you only have to write the code once (hopefully :D)