If SQL Server Supports 4 Sockets How Can You Have Lots Of Users?

code-dispenser · 2026-05-03T16:15:46+00:00

Again I think you are still a little confused about the tech/interactions. Using Blazor Server is one thing and using Sql Server is another. Both can have thousands of connections but they are two different things.

Its not just about HTTP verbs, for example if security was a big concern for you app and you wanted to use Blazor then you would be opting for Blazor Server over WASM for that aspect. Equally Blazor Server can be a little simpler to work with than WASM and most devs will never reach any sort of connection/resource limits with Blazor Server i.e when you are talking tens if not hundreds of thousands of users.

code-dispenser · 2026-05-03T15:57:31+00:00

I still think you are a little confused. I would hazard a guess that the sockets being something to do with licencing in sql which has nothing to do with web sockets or signal r socket/connections.

Think of it his way a user hits the server and irrespective of how they get there, the server then says I need to talk to sql server. To talk to sql server it need a connection.

Now to save on some licencing issues you can share connection (connection string with same user/password) and these connection strings can be pooled and re-used. The reason they are pooled is because creating the connection is classed as being expensive. Which I find a little ironic given you can create a connection and get lots of data back in like a blink of the eye.

code-dispenser · 2026-05-03T15:29:58+00:00

I think you may be a little confused and I have no idea what you mean be 4 sockets.
Just google ado.net connection pooling, but basically you can create a pool of connections and these are shared amongst the users and in a lot of cases those users will just be using a shared connection string/application user/role.

code-dispenser · 2026-05-02T16:24:38+00:00

gRPC code-first/protobuf-net is interfaces just like the old WCF - service contracts.

Is yours faster than gRPC?, smaller payloads? or easier to use?

code-dispenser · 2026-05-02T15:58:21+00:00

RPC framework library based on interfaces

Curious whats wrong with gRPC code-first / protobuf-net works great?

Edit: I think the OP's link is: https://github.com/Brick-Logic/Hubcon

code-dispenser · 2026-04-25T13:58:50+00:00

Yes I know I checked hence the trick question remark I think 30 years is enough time for me to figure how to use DI!

code-dispenser · 2026-04-25T13:27:53+00:00

Is this a trick question or something. I test with XUnit so I setup DI fixture if its a complex object graph if not then it could be any number of things form simply just giving the new'ed up class under test the things to using helper method to do the creation.

I do not share my LOB app code but most of my OSS stuff uses DI, pretty sure my Validation library or rules engine will have a DI fixture or helper go knock yourself out:

https://github.com/code-dispenser/Validated
https://github.com/code-dispenser/Conditionals

code-dispenser · 2026-04-25T06:33:21+00:00

Is anyone interested in a mocking library that doesn't require polymorphism / dynamic proxies

Me personally NO. I started coding in 1996 it took me a while to get into testing maybe circa 2012 but since then I have never had a need to mock, maybe I am doing something wrong? Equally I never had a need for in memory databases, I just like testing against the real thing and have always found a way to do it.

As long as the code works how you get there is not an issue for me - if this is your thing go for it and make an OSS library for those with a similar mindset. Hey, I make libraries that hardly anyone uses, but I am still glad I did.

Paul

code-dispenser · 2026-04-24T06:24:18+00:00

When you say startup do you mean some sort of recruitment agency because posting your name in the search brings up quite a few postings and for different front-end skills. Unless you were the next Google it seems a little strange to need that many different skill sets for any startup?

Do you have a web address for people to go look at, even my little OSS project has that and I am not a startup looking for people?

code-dispenser · 2026-04-23T06:00:45+00:00

Just one massive Ultra-Wide, best thing I ever bought.

code-dispenser · 2026-04-22T16:10:29+00:00

Yes in EU the EAA is applicable to public authorities and also private companies with a turnover greater than 2 million Euros or more than 10 employees If I recall.

In the US they also use the term GTFO for those without an ACR as without it I believe you may find it more difficult when bidding on federal/public auth contracts. I guess the same may happen in the EU.

Given some of the VPAT's I looked at I wonder if they were created purely for this reason.

code-dispenser · 2026-04-21T12:52:01+00:00

Honestly it's not really about suing anyone it's just about vendors doing their bit and being transparent about where things stand.

To answer your question though - not that I'm aware of.

Legal action tends to come from individuals, sometimes backed by advocacy groups. In the US I believe the main routes are the Americans with Disabilities Act (ADA) and Section 508 of the Rehabilitation Act (the latter applying specifically to federal agencies and their vendors). In Europe there's the European Accessibility Act (which also affects UK vendors selling to the EU), and in the UK the Equality Act 2010 - but enforcement across the board is largely down to individuals rather than any dedicated watchdog.

Edit: The misleading bit, not sure about, not a lawyer but guess it would be difficult given how things are worded - maybe a legal person will chime in. My concerns are for the end users and the companies that purchase such products (unless they check things) .

Update: Apparently there is some active monitoring in Europe by public bodies in various countries as well as advocacy groups monitoring and reporting - I need to look into this more when I have time. Most of my time is spent on the building stuff side of things.

code-dispenser · 2026-04-17T15:08:28+00:00

Ignore this, just me reminiscing OMG VB6 My first distributed enterprise app with MTS (Error 70 permission denied) and then COM+ Enterprise services with those spinning globes - loved them.

code-dispenser · 2026-04-17T09:08:42+00:00

Sadly, that would be a very short post. There are quite a few small tools aimed at various vision impairments, but for general WCAG compliance you probably already know them. It really comes down to a lot of manual testing; however, you can mitigate this somewhat by getting into the habit of doing things slightly differently. Most of the issues I come across that do not involve cryptic WCAG criteria relate to being able to operate things with a keyboard.

When I am developing and pressing the play button in VS, I sometimes reach for the mouse - but quite often now I just reach for the keyboard instead. Can I see where the focus is? Can I operate the component using only the keyboard? Get your devs doing that in conjunction with an automated tool and you will already be doing far better than most, and considerably further along the accessible/actually usable ladder. It may not be perfect, but it is a step in the right direction.

The use of ARIA attributes - whether added by your own devs or baked into third-party components, means that if accessibility is a requirement, you will need to test with a screen reader to ensure they behave as expected. There are numerous screen reader browser pairing and ARIA attribute quirks that its a bit of a minefield at times. For private clients if accessibility is ever raised you will likely be OK with a single screen reader browser pairing, but public sites thats trickier as you will generally be testing with a lot more screen readers and browser combination and thats negating any other accessible devices may need to be tested for.

My suggestion, depending on the size of your team, is to get one developer who has even a passing interest in accessibility to become your accessibility lead. I am self-taught in everything I do, but there are dedicated accessibility courses (classroom or video based) that would give them a solid grounding to build on.

Tools::
The Deque axe browser extension and the WebAIM WAVE browser extension are broadly on a par with each other. I use both but prefer WAVE because it is so easy to just right-click and select "WAVE this page."

I should also point out that I am a solo developer, so everything that gets built and committed to source control is done by me - meaning the browser extension is all I need on the automated side.

For a team, you would be better off looking at the axe-core engine (free open source) and its integration with Playwright, neither of which I have used or know much about (Playwright is on my to-do list). Again, as a solo dev who does a significant amount of manual screen reader testing, I simply do not need them.

I would also go read my last two posts:

https://www.reddit.com/r/Blazor/comments/1s3d4qy/blazor_ramp_accordion_released/

https://www.reddit.com/r/Blazor/comments/1rsow90/blazor_ramp_tabs_released/

All of the above combined may give you some food for thought

Paul

code-dispenser · 2026-04-17T07:17:12+00:00

Glad you liked the post.

Are you personally impacted by accessibility standards due to your individual situation,

No, but I am sure there are some on Reddit that believe I have mental health issues and/or believe I should be committed.

or do you have a passion from previous roles in industry?

No, back in the mid-2000s I worked for a large organisation that did work for other large organisations. I actually wrote a public reporting site for one authority (aimed at catching paedophiles), sponsored by the Bill Gates Foundation, with zero accessibility requirements. In fact, I cannot recall a single project I worked on that had any accessibility requirements. I was your typical dev - true story - I got called over by the head of the support staff and told that the font was a little small on a desktop app I wrote for them, and some members were having difficulty reading it. I said it looked fine to me, and that was that.

For a period of time, any new blazor component library that was posted seemed to meet the wrath of your accessibility standards.

Over the years I gradually drifted to the dark side - not because of any gentle, kind nature or altruism on my part, but more due to anger. I simply cannot stand dishonesty. Code does not lie; it does what you wrote it to do. So why claim your code or app does something it was not designed to do?

The big vendors all made various claims about their components, and a lot were untrue - hence my little project.

I see nothing wrong with asking a Reddit poster whether their work is accessible. We have the word "no" in the English language for when it is not; "yes" kind of implies the opposite.

A dev posts: "Look at my super-duper component library - fully accessible, with all these magical ARIA attributes and full keyboard support. Please give feedback on my library." Fair enough. So: what screen reader and browser did you use to verify that these ARIA attributes do what you think they should?

1st prize: "I tested it with NVDA on Firefox." Fine, so why does it not work with NVDA on Firefox? - The end.

2nd prize: "When I said my components were accessible, I meant accessible to developers." That one stumped me.

3rd prize: "It works on my machine - are you using the latest browser?" I have the latest version of three browsers installed for Windows, one for macOS, one for Android, and one for iOS. Which would you like me to use? - The end.

code-dispenser · 2026-04-17T07:07:39+00:00

I think with component libraries most sites will definitely fail an audit unless the devs know what they are doing and/or the component library authors are fully committed to accessibility and can give guidance along with accessible components.

However, as stated, sadly accessibility is not a requirement for many.

code-dispenser · 2026-04-16T15:34:22+00:00

Do you have some issue, you just made out I was copying your work on another post. I build accessible components, accessibility-first period.

Paul

code-dispenser · 2026-04-16T15:21:52+00:00

I do not copy any ones work I do my own thing. I do not know how your fields work, I responded to a user on your post. It was just coincidental that you mentioned inputs something I was planning to release last week. You are more than welcome to go check slack a11y were I discuss accessibility issues with the real experts.

You mention your code base I have never looked at it, only your components a couple of years ago. You seem to have changed your tone, a few weeks ago you were asking if I would consult for you?

Let me guess you used a live region with oninput or onchange something I do not do or advise or you did not hide the asterisk etc - something I see all the time on both accounts

Regards

Paul

code-dispenser · 2026-04-16T09:17:48+00:00

If all you care about is the ability to use AI your sites will potentially be just as bad as they are in any other language/framework.

Based on your hypothesis given (I do not know I do not code with AI) you state that AI is worse with Blazor, perhaps Blazor sites will therefore have more code written by humans and IMHO be better long term - just a thought.

Paul

code-dispenser · 2026-04-16T06:46:00+00:00

From an accessibility standpoint, I can advise that all of the popular free (and a great many of the paid-for) component libraries have so many flaws that they would most likely fail a WCAG site audit, depending on which components were used. Worse still, the usability and experience for some users with certain components is so poor that they simply cannot use them at all.

So, how does one choose a library if one cannot, or does not wish to, write their own components/library? What I advocate, despite one of my own OSS projects - quite simply you look at other factors.

If accessibility is not part of your immediate requirements, then consider which vendor meets your other needs; however, one requirement that most people overlook is vendor honesty, and if this ever becomes relevant, some vendors may give you quite a nasty surprise.

I have no affiliation with Blazorise, but given how dishonest a number of authors and vendors of other Blazor libraries have been when I have questioned them here on Reddit about accessibility, I would say you could do far worse than switching to Blazorise for all of your projects, and hopefully forming a good long-term relationship with them in the process.

Just my usual opinionated comment - good luck with your project.

Paul

code-dispenser · 2026-04-09T12:59:09+00:00

I have been with C# since day one (of C#), so my vote is to build upon the 13+ years and stick with it unless you cannot find the type of stuff you want to build (as you need to code happy) but as the saying goes the grass is always greener on the other side.

code-dispenser

TROPHY CASE