Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 1000391
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 16, 20262026-05-16T07:30:19+00:00 2026-05-16T07:30:19+00:00

I’m thinking about building an application with a RESTful web service. My thought is

  • 0

I’m thinking about building an application with a RESTful web service. My thought is to build the RESTful (json, etc) part of the application as a standalone, and then the frontend (e.g. html/css/js/etc) as a client to that service, although not through js, I’d like the web page to work without js, so probably using something like LWP to make the calls. Basically the result is 2 separate apps. Is this a bad idea? good idea? I realize this is somewhat subjective.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-16T07:30:20+00:00Added an answer on May 16, 2026 at 7:30 am

    I think it’s a good idea.

    It means that at the end of it:

    • You’ll have a full API with at least all the functionality of your native graphical interface. So you won’t end up with any functionality in your graphical interface that is not available as a service.

    • You’ll avoid some duplication of effort, because all the effort you go to in order to get the graphical interface working properly will also be reflected in the web service because they use one and the same function. Fix a bug in one and it is fixed for the other.

    • This also means there is consistency.

    • Automated testing is potentially easier.

    • It’s good to keep things modular especially in open source as it makes it easier for someone to then go out and write a separate graphical interface to your service, or even to modify your service while using the same graphical interface.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

No related questions found

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.