Thanks Mariano,Let me put it this waywhich products / libraries should i look at to develop a hosted / web based business application using VAST ?- Seaside- any othersI was trying to find some examples in the VAST 9.2 docs
--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to va-smalltalk...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/va-smalltalk/CAOUkibG9ZWFA%3D8xD95RJQoj1u1D%3D0_9FOPxFYtfJaqK3F11c8A%40mail.gmail.com.
1. how do I fetch willow or clone any repository from github and load it in VAST 10.0.0.2
2. fot vastgoodies is the usual way to download the .dat, import all its contents and then load
regardsOn Monday, 2 December, 2019 at 9:04:34 pm UTC+5:30 maria...@instantiations.com wrote:On Sun, Dec 1, 2019 at 10:27 PM Sanjay Minni <sanjay...@gmail.com> wrote:Thanks Mariano,Let me put it this waywhich products / libraries should i look at to develop a hosted / web based business application using VAST ?- Seaside- any othersI was trying to find some examples in the VAST 9.2 docsHi Sanjay,Yes, I would say Seaside is a good first start. You can combine it with Twitter Bootstrap which is in http://vastgoodies.com/One comment is that all the #call: and #answer: philosophy of Seaside seems already outdated to today's standards. One of the reasons is that such behavior uses full page requests, which everybody tries to avoid now. So...at the very least, you would want to make your application with AJAX everywhere.But... if you are starting from scratch, I would use other 3er parties tools build on top of Seaside for that purpose, such a Willow (which even runs on VAST): https://github.com/ba-st/Willow
Finally, there are some examples of Seaside in the docs but those are mostly about how to package VAST to make really small runtime images for production. As for Seaside itself, you have many books around in their website.Best,--Mariano Martinez Peck
Software Engineer, Instantiations Inc.
--
You received this message because you are subscribed to the Google Groups "VAST Community Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to va-smalltalk...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/va-smalltalk/ea1fbb56-150c-429d-afcc-c396849f649cn%40googlegroups.com.
| |||||||||||||||||
After reading the thread, to clarify, web services can be broken down into two categories, SOAP WS and REST. They each work differently with SOAP being more heavy handed and REST being lightweight, usually using JSON to package data. So, if you wanted to get today's weather from a weather service and display it on your webpage, then you'd probably want to use REST. OTOH, if you worked at a bank, transferring money via a WS, where security is a concern, then you might use SOAP. Actually, there used to be many SOAP vs REST arguments amongst various groups, with each group claiming, 'My way is better than yours.'
The VAST documentation on SOAP has out of date elements, such as mentioning xmethods and I have no clue how REST capable ST is.