M
Mike Fechner
Guest
+1, Jeff Von meinem Windows Phone gesendet Von: Jeff Ledbetter Gesendet: 08.05.2015 19:03 An: TU.OE.Development@community.progress.com Betreff: RE: [Technical Users - OE Development] AppServer to non-ABL clients RE: AppServer to non-ABL clients Reply by Jeff Ledbetter I am all for writing your AppServer applications in a way that different adapters can be plugged-in and used as necessary. However, if native communication is available from both sides, why wouldn’t one choose that? Jeff Ledbetter www.roundtable-software.com email: jeff.ledbetter@roundtable-software.com skype: jeff.ledbetter From: Marian Edu [mailto:bounce-medu@community.progress.com] Sent: Friday, May 8, 2015 11:52 AM To: TU.OE.Development@community.progress.com Subject: Re: [Technical Users - OE Development] AppServer to non-ABL clients Re: AppServer to non-ABL clients Reply by Marian Edu not the first time have heard appsrv applications labeled as 'legacy' by PSC peoples... abl is still 4gl, that doesn't mean everything written in it is legacy but as Gus replied when I was acting puzzled 'legacy' might mean something proven to be working, out of alpha/beta 
else, Thomas seems to imply binary and proprietary means more or less the same things... I can understand the virtues of binary protocols but those can be open so everyone can write 'adapters' that can adhere to the protocol so the 'service' is open to anyone. On 08/05/15 18:28, Jeff Ledbetter wrote: From: Jeff Ledbetter Post: RE: AppServer to non-ABL clients Posted in: Forum Link: http://community.progress.com/community_groups/openedge_development/f/19/p/17878/63382.aspx#63382 Well, not blasphemy but not practical either. “I pretty much don't see any reason that any sort of client, and that includes ABL, java, .net to use proprietary appserver protocol anymore.” Although it is your personal opinion, you work for PSC, your opinion has weight so it is a bit irresponsible to say that. There are many applications which use traditional AppServer protocols. They are therefore deemed “legacy” and outdated because they have not adopted yet another technology offering from PSC? Why add the additional layers, adapters and what not, if they are unnecessary for a specific configuration? Jeff Ledbetter www.roundtable-software.com email: jeff.ledbetter@roundtable-software.com skype: jeff.ledbetter From: Matt Baker [ mailto:bounce-mbaker@community.progress.com ] Sent: Friday, May 8, 2015 9:59 AM To: TU.OE.Development@community.progress.com Subject: RE: [Technical Users - OE Development] AppServer to non-ABL clients RE: AppServer to non-ABL clients Reply by Matt Baker This might sound like blasphemy, and its a personal opinion...one could say using pure appserver protocol is completely legacy and there is no reason to use it anymore. I pretty much don't see any reason that any sort of client, and that includes ABL, java, .net to use proprietary appserver protocol anymore. Between JSON as a message encoding, REST as a set of protocol best practices/standards, and HTTPS as transport layer you can write any client: but it "mobile", "desktop", "web", or "batch" or simply a perl script, and have it all talk to the same backend without worrying about proprietary stuff. Look at the NoSQL databases out there, All the ones I'm familiar with all support HTTP+JSON as their primary protocol. PAS for new stuff, and REST adapter for legacy make this possible in the OpenEdge world. Mobile absolutely requires that you use HTTP+JSON. Just consider everything "mobile" and you're halfway there. Stop receiving emails on this subject. Flag this post as spam/abuse. -- You were sent this email because you opted to receive email notifications when someone created a new thread. To unsubscribe from: - ...only this thread, disable notifications at http://community.progress.com/community_groups/openedge_development/f/19/p/17878/63382.aspx#63382 . - ...all email notifications from Progress Community, navigate to "Settings", click on the "Email" tab, then under the "Email Configuration" section, set Send Notifications to "No". -- m.edu keep it simple http://www.ganimede.ro http://ro.linkedin.com/in/marianedu medu@ganimede.ro mobile: +40 740 036 212 skype: marian.edu Stop receiving emails on this subject. Flag this post as spam/abuse. Stop receiving emails on this subject. Flag this post as spam/abuse.
Continue reading...
else, Thomas seems to imply binary and proprietary means more or less the same things... I can understand the virtues of binary protocols but those can be open so everyone can write 'adapters' that can adhere to the protocol so the 'service' is open to anyone. On 08/05/15 18:28, Jeff Ledbetter wrote: From: Jeff Ledbetter Post: RE: AppServer to non-ABL clients Posted in: Forum Link: http://community.progress.com/community_groups/openedge_development/f/19/p/17878/63382.aspx#63382 Well, not blasphemy but not practical either. “I pretty much don't see any reason that any sort of client, and that includes ABL, java, .net to use proprietary appserver protocol anymore.” Although it is your personal opinion, you work for PSC, your opinion has weight so it is a bit irresponsible to say that. There are many applications which use traditional AppServer protocols. They are therefore deemed “legacy” and outdated because they have not adopted yet another technology offering from PSC? Why add the additional layers, adapters and what not, if they are unnecessary for a specific configuration? Jeff Ledbetter www.roundtable-software.com email: jeff.ledbetter@roundtable-software.com skype: jeff.ledbetter From: Matt Baker [ mailto:bounce-mbaker@community.progress.com ] Sent: Friday, May 8, 2015 9:59 AM To: TU.OE.Development@community.progress.com Subject: RE: [Technical Users - OE Development] AppServer to non-ABL clients RE: AppServer to non-ABL clients Reply by Matt Baker This might sound like blasphemy, and its a personal opinion...one could say using pure appserver protocol is completely legacy and there is no reason to use it anymore. I pretty much don't see any reason that any sort of client, and that includes ABL, java, .net to use proprietary appserver protocol anymore. Between JSON as a message encoding, REST as a set of protocol best practices/standards, and HTTPS as transport layer you can write any client: but it "mobile", "desktop", "web", or "batch" or simply a perl script, and have it all talk to the same backend without worrying about proprietary stuff. Look at the NoSQL databases out there, All the ones I'm familiar with all support HTTP+JSON as their primary protocol. PAS for new stuff, and REST adapter for legacy make this possible in the OpenEdge world. Mobile absolutely requires that you use HTTP+JSON. Just consider everything "mobile" and you're halfway there. Stop receiving emails on this subject. Flag this post as spam/abuse. -- You were sent this email because you opted to receive email notifications when someone created a new thread. To unsubscribe from: - ...only this thread, disable notifications at http://community.progress.com/community_groups/openedge_development/f/19/p/17878/63382.aspx#63382 . - ...all email notifications from Progress Community, navigate to "Settings", click on the "Email" tab, then under the "Email Configuration" section, set Send Notifications to "No". -- m.edu keep it simple http://www.ganimede.ro http://ro.linkedin.com/in/marianedu medu@ganimede.ro mobile: +40 740 036 212 skype: marian.edu Stop receiving emails on this subject. Flag this post as spam/abuse. Stop receiving emails on this subject. Flag this post as spam/abuse.Continue reading...