[Info-vax] First ship poll: When will the first native x86-64 compilers ship ?

[Jan-Erik Söderholm]

Den 2022-04-17 kl. 04:04, skrev Dave Froble:
> On 4/16/2022 7:00 PM, Craig A. Berry wrote:
>> On 4/16/22 5:25 PM, Dave Froble wrote:
>>> On 4/16/2022 6:14 PM, Arne Vajhøj wrote:
>>>> On 4/16/2022 11:02 AM, Jan-Erik Söderholm wrote:
>>>>> Den 2022-04-16 kl. 13:28, skrev Bill Gunshannon:
>>>>>> On 4/15/22 22:10, Dave Froble wrote:
>>>>>>> On 4/15/2022 7:25 PM, Arne Vajhøj wrote:
>>>>>>>> Cobol, Basic, Pascal, C etc. is just not the optimal language
>>>>>>>> for writing a new web service.
>>>>>>>>
>>>>>>>> Not on any platform.
>>>>>>>
>>>>>>> Really depends on the web service, doesn't it?
>>>>>
>>>>> And on the *definition* of "web services".
>>>>
>>>> There may not be a formal definition, but most developers have
>>>> a common understanding what such a thing is.
>>>>
>>>> Something like: a service intended to be used by client applications
>>>> based on web protocols typical XML/HTTP(S) or JSON/HTTP(S).
>>>>
>>>> Arne
>>>>
>>>
>>> Well, there you go again, refining the definition to match your claims.  Of
>>> course that makes you right.
>>>
>>> How about anything that offers some service that might be needed over the
>>> internet?
>>
>> Nope.  That would be an internet service.  A web service uses some
>> version of the HTTP protocol.  While that doesn't necessarily imply
>> REST, the simplicity of REST has made web services largely eclipse older
>> client-server protocols such as SOAP or Java RMI.
> 
> Having looked at REST, I find it as difficult and performance robbing as 
> the "rest" (no pun intended) of the "standard" protocols.  We have done 
> some testing.  We find that using sockets with no additional overhead has 
> given us the best performance and the least overhead and the simplest 
> programming.
> 
> I will admit that we already had a protocol in place, so that helped.
> 
> So, if we cannot be considered having a "web service", we don't care, and 
> we think our approach is better.
> 
> We still call them our "web services".

Yes, of course you do! :-) That is what the customers want to hear, right?
They probably do not care if it is correct or if it is just sales talk.


> 
> I've written a HTTP(S) PUT utility using our socket communications, but 
> only use it when the trading partner insists on HTTPS.
> 

Most sane developer would not write that themself, but deploy a web
server that already have all that built-in out of the box. You "only"
have to supply the backend server process that has the business logic.

Process management, adding or removing processes as needed, access
and authentication control and so on are already handled by the
web server.