Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
This might seem like a strange question, however it suddenly hit me that i might be doing this wrong...
So, I've been working on an application for a while, and recently we switched from open source solutions to Microsoft solutions for the backend (OS, Database, Webserver).
Now, previously I've been using standard java web services for pulling and pushing data into our DB, however the vast majority of that has now been replaced with application roles and direct DB access from our clients (This is internal, no less of a security concern)
We still have a single application that i had planned to continue the use of web services with, this simply works as a single login, patching and launch platform for our other software, a basic portal. However reading up on .net services, web api and WCF I'm suddenly struck by the sensation that perhaps web services are in fact not the way to go here.
So basically, the services perform the following functions
Taking a username/password for the client, and confirming successful
login.
Retrieving the version information for a list of installed
applications.
Changing the users password Resetting the password in the event it
was forgotten.
Now, are web services really the "best" (or more, simply a reasonable) way of providing this functionality, or would a more standard client server setup be a more reasonable way of achieving this, or perhaps i'm simply over thinking the case?
It's really difficult to say what the best way for your case is and I think it's more subjective than anything else.
That being said, while using a WCF service might be an "overkill" for something so simple. Building a server-client setup from scratch definitely sounds like an overkill. The base WCF service does a lot of the hard lifting for you with a relatively low cost and almost 0 cost in development. Unless it's becoming a performance bottleneck, I don't see why you'd switch solutions.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I'm in a situation where I do not have the option to connect directly to a database (the typical ConnectionString and DBContext way), but instead, I'm forced to use a RESTful API to get and post data from, and to the database.
I difficult to explain, so here's a tiny architectural graph instead.
Easy to see, the web application can talk with the REST API, but it CANNOT connect directly to the database
PROBLEM
I'd love to use the built-in authentication system that ASP.NET Identity provides, but I'm going in completely blind. I have not been able to find any examples with REST API calls to get users, roles, etc.
I hope that some of you might be able to lend a hand. The architecture is as it is, and it's out of my hands to change it.
My team is currently using a similar system. Our solution was to use Authentication Forms, which we found easy to setup using this article. Granted it is a bit outdated, but it works for what we wanted to accomplish with a small amount of time.
Sorry, I know Its not much, but it was a very easy tutorial to follow. Feel free to ask for any more examples as you work through it!
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 6 years ago.
Improve this question
I want to stress my .net web service, It feels like something is limiting the concurrent connections I can have.. even when trying from 2 different computers on them server the results were pretty the same. (All of this is done locally, server and clients are on local network so response time is very fast)
So is there a settings I need to change in my server machine to allow more incoming connections?
There are various things that can limit the amount of processing possible, each of which require research to see if they apply. So you might want to add more to your question about what has been verified today.
Regardless, based on your information I would assume that SessionState is enabled. This, with default behavior will limit processing to a single request at a time for each client due to synchronization locks for guaranteed read-write ability. I assume this is the root cause of what you are seeing today. This StackOverflow post talks about this specifically
Others have posted various details in the comments that can help also.
I have found though that load testing is best done from outside sources as well to ensure your entire production pipeline is involved. (Network components, etc)
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
Some background: We have 3 websites that are all part of a standard workflow. Each website handles a different part of the workflow.
Website 1 is for sales (pricing, sales, etc)
Website 2 is for engineers (implementation, coding, testing)
Website 3 is for reporting (used by all but primarily for administration and management)
We're gearing up to add notifications in a way that's a lot like how StackOverflow does notifications. I actually posted this on Meta Stackoverflow because that seemed like the best route, but the question didn't get very far. The notifications in our context would be things like "John Smith's timesheet is late" or "You have been assigned to a project"
Now I'm curious as to how other developers have set this up. I'm primarily worried about code repetition and maintenance at this stage.
Specifically, should each website be responsible for implementing its own notification client? That seems like it'd be really easy for code bases to get out of sync. But at the same time, even if you build a library you still need to handle the HTML templates somehow. How much duplication of functionality is acceptable? I'm at a loss here.
As you can tell, I'm not really sure where to start. If this were for a single website it'd be a different story, but implementing it across multiple websites at the same time has be puzzled.
Some miscellaneous facts about our stack:
Server side: ASP.NET MVC 4 (C#)
Cliebnt side: jQuery + Knockout
Database side: SQL Server w/ LINQ to SQL
IE not supported.
You can also do something like google +1 button. Link to a javascript common to everybody and have a custom html tag that will indicate where to put the data with configuration if needed.
Since you own all the websites, you can put everything in it's own .dll and add it to the solution of each solution.
Are you need something like Redis.io? There is Publish-subscribe in Redis.io.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I am looking for the best way to implement, let's say a middle tier.
In the company I working for, we have two systems written with different programming languages. Each one must communicate with a third system via xml (rest and soap).
The first thing that came in my mind was to create a web application which would accept the calls from our internal systems but I stopped this implementation as I faced some issues regards the soap serialization (How could I do this?).
Except this I thought of WCF but I don't know if it is an appropriate solution for my case.
So, I would like to know which is the best way to implement this.
I'll appreciate any comment
Thanks
You should use WCF for the middle-tier since it provides you with everything you need.
Serialization
Interoperability with Other Web Services Platforms
Interaction with Applications built on other technologies, such as J2EE application servers, that support standard Web services. These applications can be running on Windows machines or on machines running other operating systems.
Security
SOAP All Version and REST
Bindings
Protocols
Discovery
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 12 years ago.
Improve this question
I'm looking for a blogging site to host my ASP.Net/C# (and possibly other web related programming) technical blog - where should I create such blog?
BTW, it's a shame that SO does not offer blogging services.
Note: I would create it on http://weblogs.asp.net, but it requires to be a highly active member on their site.
I would personally suggest WordPress if you'd like to get up and running quickly. I am sure a thousand people have a thousand different opinions on what is good and what isn't. I like WordPress because the templates are easy, there are some nice features, they will give you your content in XML form for backup or moving to another service in the future and it links well with LinkedIn and other services to share your posts and drive in traffic.
WordPress, Drupal and Joomla are all good choices for running a blog if you choose to use a dedicated hosting service (e.g. hostclear, etc.), and they're all extremely well supported by their dedicated community.
Here's a good article which offers a high level comparison of the three:
http://www.goodwebpractices.com/other/wordpress-vs-joomla-vs-drupal.html
Speaking from personal experience, I think it's worth getting a decent hosting service like HostClear, they're pretty cheap these days and gives you domain registration for free too. I've been running my blog for about 8 months now, at less than £3 a month and I've been more than happy with the service I got! And having tried both Joomla and WordPress, I found WordPress much easier to get started with.
Toolbox.com is a great site. They have over a million members, so the audience is built in, and they have a revenue sharing program.