It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
we have centralized back office system and we keep all products information,recently our clients asked us to deploy website to them, so they can show their products on their websites , the clients have their own websites which developed on php or java or whatever , they don't like to use Iframe to show their products because of some SEO problems in Iframe, We want to deploy our E-commerce website inside their website,We want to show our website inside HTML tag such as div,we don't like to design and develop new website for any individual client, I am very interested to know your ideas , and any alternative solution.
So instead of focusing on developing a website that is embeddable, I would focus on one of two approaches: 1) Make web services/REST API, 2) Write a Javascript library.
Making a REST API
You can write web services (or a REST API) that a client could use to integrate into their site. This would expose your data/services/features to them. They would have to do a little programming of course to integrate with the services, but it's an option.
Writing a Javascript library
You can write a Javascript library that will dynamically bring in data (calling web services of course that you host) and then you can take that data and place them into divs etc.
The advantage of this is that you can tell the client something like "just drop these 5 lines of code onto your page and it will do the rest." It has a low barrier to entry for a client.
Related
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 9 years ago.
I am working on project which have functionality like Creating Team, Tournament, Play Match between teams and also scoring that match.... via web and mobile application....
So I have to implement a functionality like if a scorer enters a score immediately the scores updates on scorecard or player statics are reflected with new values,
I am using Asp.net MVC 3.0, MS SQL 2008 and Entity Framework, jQuery etc.
So please anybody can guide to achieve above functionality while taking care of site performance...
Thanks in advance......
My suggestion is SignalR
ASP.NET SignalR is a new library for ASP.NET developers that simplifies the process of adding real-time web functionality to your applications. Real-time web functionality is the ability to have server-side code push content to connected clients instantly as it becomes available.
You may have heard of the HTML5 WebSocket API that enables efficient bidirectional communication between the browser and server. SignalR uses Websockets when it is supported by the browser and the server, and gracefully falls back to other techniques and technologies when it is not. Either way, your application code stays the same.
SignalR provides a simple ASP.NET API for creating server-to-client remote procedure calls (RPC) that call JavaScript functions in client browsers from server-side .NET code. SignalR also includes API for connection management (for instance, connect and disconnect events), grouping connections, and authorization.
More about SignalR
Sample
If your issue is real time updates for an already rendered page I would use SignalR. It allows you to push data from an MVC app to a webpage. JavaScript on the website can then update the content in real time. Lookup single page application and SignalR
Here is a guide to getting started with it http://www.asp.net/signalr/overview/getting-started/tutorial-getting-started-with-signalr
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
I need to know the technical difference of those files. Which one is the best option?
When and why should we use it?
I need a human answer, not the MSDN links.
.ashx files are used for handling HttpRequests and modifying HttpResponses; you can pretty much make them do whatever you want. I have seen them used for things like serving PDFs and doing server-side processing and then redirecting. See here for more info.
.svc files (which were not mentioned in your question) are part of MS's new Windows Communication Foundation which is for SOA development. WCF supports SOAP, REST and a lot of other cool stuff.
.asmx files are an older means to host SOAP services. They are often accompanied by asmx.cs files (or .vb) which contain the actual methods behind the service. See here for more info. This is a legacy technology and I would recommend using WCF instead in new development.
[WebMethod] attribute is used to denote the methods surfaced in a SOAP service hosted by an asmx. See here for more info.
The .axd extension is used by generated web services used for many different things. (E.g. MVC3 uses axd web services to serve MS specific javascript) I don't think you would ever create an axd file, but I could be wrong... at least I never have. See here for more info.
Which one is the best option?
They are different tools used to solve different problems. When and why you should use each one depends on the job you are trying to accomplish. Lower level handling of your web application's behaviours can be achieved with ashx files. If you want to provide more standardized services, I would recommend using WCF and svc files. Please provide us with more information about the task you are doing so we can help you pick one.
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
as the title says, I want to develop a browser multiplayer game with HTML5.
The game will be something like "risk", the turn-based strategy game. I decided to develop with HTML5 and the new canvas.
But the problem is on the server side. When I google, I only get answers, where people use "System.io", "node.js" etc. for that.
So my question is:
Is ASP.NET - especially MVC 4 - a bad choice for my purpose? I would like to do that with asp.net, but of course not when there is an easier/more suited option.
Some people say asp.net is not suited for that, it's too complicated and so on.
But I ask you pros out there :D
Would you consider developing a game like that with asp.net mvc 4 or better stick to other solutions with system.io and node.js and other frameworks? (php?)
I hope you can help my out, that stresses me for weeks now :(
Thanks in Advance!
Greetings from Munich
Tornister
Asp.net, especially MVC is well suited to develop an html5 based game.
A turn based game, is not very different from a web based chat. Where you send messages between members via the server.
To design a scalable solution, you got to use the right methods though.
You have various options to communicate between users.
Libraries like SignalR would help. If you do want to do it yourself, the most efficient method is to use a IHttpAsyncHandler and ajax requests. In MVC the equivalend it AsyncController.
Frameworks like node.js are designed to be async, and thus well suited. Php out of the box is not a good choice for such applications as it doesn't support async requests.
To sum it up, asp.net is not a bad choice, but you need to know how to use it. If you are more comfortable with another framework like node.js, then you should choose that one. Familiarity reduces a lot of development time.
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
I'm developing an ASP Web API project and using KnockoutJS as the client side technology. To the best of my knowledge there are no examples projects or any kind of sources available in internet for these two technologies yet. If someone has used these two technologies for their development, it is great if you can provide some links here (If there are online sources). I am posing this not as a question but to get some online sources about these technologies to one place (Because as I know there are no online sources yet). If someone know any sources about the projects which have used these two technologies in there architecture, it will be a great help for me (Since there are no online sources).
Thank you.
You should checkout upshot.js, Steve Sanderson's library for interfacing with WebAPI REST services. It is designed to complement knockout.js when building single page applications, facilitating communication between the view model (knockout) and the back end (WebAPI).
Here's a relevant SO post:
Where can I find Upshot.js examples and documentation?
I don't really have any links to share, but on the server side WebAPI outputs JSON by default and client/KnockoutJS side you are just consuming JSON. I use jQuery's .getJson() method and update my KO view model with the return data.
Check out John Petersen's blog for some good Web API samples.
Technically, Knockout.js doesn't help with accessing a REST API specifically Knockout with JSON. So, yea it works fine and I've used to with the Web API no problem. There is the Mapping plugin that helps with mapping the data to your view models which may be useful to you: http://knockoutjs.com/documentation/plugins-mapping.html
Backbone.js is meant to work with REST APIs (like Web API) and there is a project that makes Knockout work with Backbone (https://groups.google.com/forum/?fromgroups#!topic/knockoutjs/SAESwAqjfK4). I haven't used it so I don't know if it works well or not.
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 11 years ago.
As far as my understanding goes Modules kann be used to split an Application into different parts.
A big advantage seems to be to be able to load Module after Application Start, to get a better Startup performance.
I personally would like Modules to make me able to have an own Code Sandbox for the Module Code.
So neither the Main App Code nor the Module Code should influence each other. But for examples CSS Styles from modules influence the Main Application an visa vers.
My Question:
1. What can I use Modules for beside Runtimeloading ?
2. Are there options to run code in an own sandbox ? For Example via Loading swf assets ?
What can I use Modules for beside runtime loading ?
You can divide your application into distinct pieces - For example, you may only need to update the shopping cart portion of an application rather than the entire application. This lets you do that without deploying the entire application again. This forces good abstraction and means less regression testing / bugs.
Another benefit is securing the swf files themselves. I've written back end applications where a user might be able to get to the orders screen, but not the user management screen. Because each are a modules, the client never even gets an opportunity to see (or decompile) the user management swf code - because I can validate the user's session server side when they try to load a module. This is an extra layer of protection.
Memory management -its not just about loading the application, but how much processing it takes to have all that functionality loaded at once. If a user only needs one or two screens, why load the other 98 screens?
Portability and code reuse. You might use the "order viewer" module in both a consumer facing application and a back end tool. Those are most definitely not the same application, but they both need the basic functionality of the order viewer. Better yet, an entirely different application could use that same functionality.
Are there options to run code in an own sandbox ? For Example via
Loading swf assets ?
There are special considerations for communicating between modules, here is a good read for you:
http://livedocs.adobe.com/flex/3/html/help.html?content=modular_2.html
You can allow a module to deal separately with its styles by creating a new SystemManager for its flexModuleFactory, and you can load it into a separate applicationDomain for security purposes.
Not really an answer to the question you asked, but it addresses the underlying problems you were having.
We used modules at my last job to allow us to develop and add new functionailty on the fly--the path to the module would be stored in a database and loaded at runtime.
HTH;
Amy