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 have 3 JSF projects (let's say A, B, C) each having same database, server. I want to merge projects A, B into one and make it available over internet, similarly merge project A, C into one and make it available over intranet.
Intranet website will need an authentication layer, I will probably add JDBCRealm authentication.
What is the best procedure to do this, I want the code to be reusable. Do I need to use EJB?
Not sure I understand the question. But if you just want advice on how to manage projects and dependencies between them I would take a look at maven.
http://maven.apache.org/guides/mini/guide-multiple-modules.html
I have a setup I really like, it's basic but I will describe it anyway:
myproject-webapp: This module / project has JSF facelets, controllers, and other things specific for the web portal. It is the topmost project in terms of dependencies.
myproject: This module has the domain classes and the specific business logic.
Whenever I start a new project it is composite of those two parts. Now anytime I write some domain or business logic code that other projects can benefit from I put that code in it's own module called "core".
Respectively any time I write some jsf or web aware code that could (and should) be unspecific I make that generic as well and put it in "web-util".
So anytime I create a new project first thing I do is declare dependencies to "core" and "web-util". This makes each project really slim code-wise and straight to the point. Boilerplate code such as as generic dao, custom converters, custom interceptors/producers/events and whatnot is immediately available.
Separate out all your concerns, that is authentication and other environment specific information (a,b, &c)
Create deployment scripts that build target specific or deploy target environment specific.
Note there is a difference in the above ( user whichever is safest).
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.
To start a new project/webapp on Node.js, I need:
Folder Structure;
Libraries (Express, RequireJS, Mocha, Bower, ...);
Software Phases - Build, Compile, Testing, ...;
...
Which is the best Stack for Large-Scale projects on Javascript/Node.js?
Thanks in advance for your help!
First thing's first, keep it simple. Every new tool you add is another dependency, and another potential stress point for the project. With that in mind, some good tools, methodologies, and best-practices for server-side javascript development are:
Folder Structure
This doesn't really matter. Just do what makes sense to you, and what you think will make sense to others if you plan to have collaborators. Search github for Node.JS projects and see how they're structured. I found one good example: https://github.com/thomasdavis/backbonetutorials/tree/gh-pages/examples/nodejs-mongodb-mongoose-restify
Libraries
The libraries you use is going to greatly depend on what type of project you're working on. Does the REST API hit a database? Is it MongoDB, redis, MySQL, Neo4J, ... ? You're going to need an interface for that.
Express is a great framework. (I believe it can start a project for you even.)
Technologies
Have you considered Coffee/Clojure-script? This extra step at compile time can save you a lot of headaches later on. Your code will also be more readable to others. Jslint is another great tool to verify javascript code. Also, I have to suggest using git for version control. If you aren't: learn it, master it, use it. http://www.git-legit.org/
Methods
Your software development strategy will be dependent on what tools you end up using as well as your own personal choices with regard to how you like to write software. I would suggest using Jenkins to continuously integrate your code, and some sort of test framework to ensure what you write is right.
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.
Do I really need a Portal ??
Always one question comes to my mind , why do people go for Portal development , can't they manage with a normal web aplication , managing the UI Page with different sections? I am sorry if my question is not valid.
Or In what scenarios do we actually need a web Portal?
Managing a UI page with different sections is fine if your users are using only your application. However, a portal allows your users to use multiple applications (and many of them not created by you) and kind of 'aggregate' their content on one page; well at least have a place which provides easy access to them on one page. The emphasis here is on multiple applications; these are applications that you as a developer may have no control over; they may have been written by a third party (such as Google, or any other developer).
The items on a portal page may not necessarily be from the problem domain that you are developing for. There's no reason why a user can't put the local weather on the same page that he's examining the inventory for his company.
Portals provide a single point of entry; that's the key point. A portal also provides some other niceties such as managed logins. If you are creating an application for a customer, and you don't have a need for a portal, a portal may be overkill (and probably is, if you have to ask).
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 develop a part of a Drupal web site. I cloned the git repository and setup the settings.php. The site is showing and I am using a dump of the MySql DB from the live server. I am 99% sure that the dump has been created without clearing the cache first. ANY link in the site is not working, so don't tell me to go to /admin/ because I can't. I tried to clean the table with cache* name without success. I have .htaccess in place. What elae I have do to do have a Drupal site working okay?
I am using Drupal 6.
Ok, I couldn't type this all in a comment, so it is now an answer...
~ "It is just that Drupal is rubbish. Now I remember why I moved away from PHP. I tried for follow Drupal's code but it is a nightmare. They should learn what OOP is (although OOP support in PHP is rubbish too)."
That comment is un-constructive, contradicting, and comical, especially considering you haven't even put in the time to know how to provide ample info for others to answer this question.
With such little info, I'd guess that Alexander is on the right track in questioning around it being an issue with your system's rewrite config.
Here are some other questions you should either have provided answers for or tried debugging already before you start blaming the platform over your ability to troubleshoot it.
Are you able to login? if not, maybe with http://example.com/index.php?q=user/login?
Any errors in the apache log? Have you tried to turn on rewrite debugging, and then any errors being reported if so?
Is mod_rewrite enabled on your local environment for clean urls?
Is your Apache config setup to AllowOverride=All for the specific virtualhost so .htaccess will pick up? If not, have you configured Apache to load that .htaccess file?
Is $base_url set correctly in the settings.php file?
What is the format the links are providing?
Have you tried disabling any custom modules via the system table?
Can you install a brand new instance of Drupal on the same system configured the same way successfully?
The platform you know well is usually going to seem much more elegant than the one you don't know much about at all.
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 12 years ago.
I have been trying to find a simple answer for a while now but I can't seem to get a direct answer?! Can someone please put it into simple terms? Thanks it would be much appreciated
SharePoint is a content management system (CMS) build with an ASP.NET front end, and an XML based backend running on IIS and SQL Server.
A good start is wikipedia:
http://en.wikipedia.org/wiki/Microsoft_SharePoint
Sharepoint is just a one stop shop portal. It allows you to manage documents, provide workflow, and collaboration. It even can be built to work like a CRM system, especially the 2010 version which is .net based.
All in all it is a good intranet tool for a company big or small. It can handle documents and provide information like when the document was updated, what was updated, checking in / out documents.
It also allows you to post notes, reminders, notifications for company wide functional groups. You can strict it to be departmental. It is a monster that is based on a SQL SERVER backend with some notorious tables. You can build lists of any sort, import Excel data, and create performance indicators for things like reports or management content.
Just a very large CMS (can be CRM) / Document Mgmt / Anything embedded from .net system.
Sharepoint is a system for shared calenders, appointments, discussions, document tracking, crm and cms solutions...
Good for internal use - but can equally be used external public face content manageable sites.
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.
This is a very newbie question.
I want to know how to create a web app to make a telephone call, most likely using VOIP protocol.
What programming languages, both client and server side, do I have to learn?
The primary question you need to answer to get started is are you looking for a computer to computer call or do you want your app to call a telephone number?
Since you specify that you want your "web app to make a call," I suspect you're looking for a way to place automated calls to a user's telephone. If that's the case, you've got a few options.
Install a VoIP server like Asterisk or Freeswitch and write code to have your web app interact with it. For Asterisk, the Adhearsion project can help by allowing you to write Asterisk integrations in Ruby. http://adhearsion.com/
Or you can use a cloud telephony service like Cloudvox or Tropo http://tropo.com (disclosure, I work for Voxeo, the company behind Tropo). These services allow you to use web programming languages and web services to talk to the phone system. You don't need to know anything about Voip to make it happen. A sample Tropo script...
<?php
answer();
say('Yes, it really is this easy.');
hangup();
?>
A side benefit to the cloud services is many of them allow your app to run over other communications channels (Tropo does IM and SMS, too).
The third option is to look into VoiceXML, a W3C standard for creating voice apps. Voxeo provides detailed docs and VoiceXML tutorials at http://vxml.org/. With a VoiceXML (sometimes called VXML) application, you can install a VoiceXML server and the associated VoIP bits or you can use a VoiceXML hosting provider. Voxeo provides both a downloadable server and hosting (both are free for developers), or a search for VoiceXML hosting will reveal a large number of options.
The answer to your question really depends on what you want to do with it. Here are 2 examples of how I have gone about it:
I developed the software for Go2Call.Com (now owned by Deltathree), and it was used for PC-to-Phone calling. In Go2Call's case, it was a Java applet for the dialer frontend that called a Windows DLL written in C++. From there, it spoke a proprietary protocol to talk to the servers which in turn sent the call to regular landlines.
A few years later, I wrote a web-based (ActiveX control) that would allow PC-to-PC or PC-to-Phone calling, and it used the standard H.323 protocol.
I would recommend starting out by figuring out what your end goal is and then looking up the necessary protocols and technologies to accomplish it.
For PC-to-PC, you can do whatever you want if both people use your software. In that case, you can figure out how VOIP works (including compression codecs, etc.) and implement it however you want.
For PC-to-Phone or when you want to call someone else's software, I'd recommend SIP since it's probably the most popular protocol. H.323 is still prevalent, but SIP seems to be taking over.
Sorry this doesn't probably tell you everything, but there's a lot to it. Hopefully, this will get you started in the right direction.
Update: Since you mentioned PC-to-PC, Packetizer has a list of standards and quite a bit of info I used way back when I did a lot of VoIP programming.
As far as books go, the books I've seen so far aren't programming-related but more about using VoIP software and installing VoIP networks.
Gizmo5 has a Flash softphone that runs in the browser: GizmoCall
On the server side, you'd probably link it up with an SIP solution in any language. Asterisk comes to mind, although it may be a bit overkill depending on whether you really wanted a full-blown SIP solution or not.
You may wish to purchase a component which allows you to add SIP functionality to your webpage, (most of these ones are ActiveX based):
http://www.conaito.com/
http://www.vaxvoip.com/
http://www.pcbest.net/
As for the language you have to learn, well what languages have you learned already? Which languages have you developed web apps with? This determines your choice of language. Using components like those listed above take some of the legwork out, but still will require probably vbscript or javascript coding client side, and those that are activeX will only work on Internet Explorer webbrowsers.
If you have no experience then you need to look seriously at what you are trying to do, why, how much time and effort you can and are willing to put in.