Skip to main content
This topic has been closed for replies.

1 reply

BenPleysier
BenPleysier
Community Expert
June 28, 2018

I have been using all of the lastest versions of WebAssist's extensions using MySQLi, specifically when I have had occasion to use eCart. It brings back memories of the golden past when Dreamweaver was at its height with the inclusion of the server behaviours panels. Ray has also been very helpful when I have had to use different payment gateways, sometimes spending 4 hours and charging for one. All in all, thumbs up.

Having said that, I have fallen in love with client-side processing of data. It allows for very fast data manipulation without having to traffic back and forth to the server. An added feature is that page refresh is a thing of the past. In this regard, large database tables of more than 3K records are better processed on the server-side.

I guess that in the end it's all a matter of taste.

Wappler is the DMXzone-made Dreamweaver replacement and includes the best of their powerful extensions, as well as much more!
    O
    osgood_
    Brainiac
    June 28, 2018

    Not sure why a page refresh should be a thing of the past, its still relevant if you're processing a product details page, which uses a different page template. On the other hand if your processing some kind of form data or simple search app using client side processing is a smoother experience. I think its more a question of where to use which one rather than one being a better solution than the other.

    O
    osgood_
    Brainiac
    June 29, 2018

    As you said, Ben is most qualified person here to answer about your questions.

    For me, server-side solutions give me a feeling of greater security... to understand what I mean see this post:

    https://community.wappler.io/t/hide-secure-data-connection/1412

    It's easy for those who are at first to commit serious data management errors.

    Another "little" problem is that the DMXzone's client-side solutions are proprietary (I mean the framework), which means that if they close, your business is over (e.g. remember InterAKT with PHAkt).


    -Michele  wrote

    Another "little" problem is that the DMXzone's client-side solutions are proprietary (I mean the framework), which means that if they close, your business is over (e.g. remember InterAKT with PHAkt).

    Yes, Wappler uses its own workflow, similar to vue.js or one of the other javascript frameworks so if you are dependent on it and not going to dive into how it processes the information that could be a big issue if they ever decide to put Wappler to bed.  It's a choice you must make depending o your coding experience. Muse died and left developers, if you can call people who used Muse developers, for dead, so it can and does happen and will happen again.

    Its much better in my opinion to roll-your-own  based on tried, trusted workflows which have a lot of open-source support and solutions.

    Initailly when you use client side scripting the page takes longer to process but is said to be quicker than server-side after that but lets get this right we are talking about huge sites such as facebook, google, linkedin of that kind of magnitude where the server is getting hit thousands of times a minute, not some small site which gets 500-1000 hits a day, in that context there is no issue to using sever-side to process information. having siad that client side is very nice as its a lot smoother for the user but there is issues as far as I know with SEO from what I've been reading......so in what context/wher you use it should be considered.

    If you're using ajax for backend admin then who cares, just be wary and careful if you intend to introduce it for all front end workflow. I suggest you read about it and what others say who are unbiased and form an opinion based on that.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices