thetoolwiz wrote:

> I noticed that RemObjects just released Remoting SDK and DataAbstract.
>
> It looks like the former lets you write service tiers easily in five
> languages (C#, Oxygene, Swift, VB, and Delphi), probably not
> appropriate for use wtih AWB.

The RO SDK is just fine for use with EWB applications, as a remote
procedure call interface. WHether it is right for any particular
application depends on its needs of course.

--

Matthew Jones

David,

<< It looks like the former lets you write service tiers easily in five languages (C#, Oxygene, Swift, VB, and Delphi), probably not appropriate for use wtih AWB. >>

Do you mean EWB ?  If so, then you can use RemObjects with EWB - the back-end uses RemObjects and the front-end uses EWB to talk to it, either directly or using their JS code as an intermediate layer.

Do a search here on the forums on "RemObjects" and you'll get a bunch of hits.

Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

<<<
David,

<< It looks like the former lets you write service tiers easily in five languages (C#, Oxygene, Swift, VB, and Delphi), probably not appropriate for use wtih AWB. >>

Do you mean EWB ?  If so, then you can use RemObjects with EWB - the back-end uses RemObjects and the front-end uses EWB to talk to it, either directly or using their JS code as an intermediate layer.

>>>

Yes, EWB. What I was thinking was that EWB is for writing client-side stuff, not middle tiers and back-end stuff.

But I'd guess that Remoting SDK could be used to build a service that EWB could talk to. That's not what I was thinking of at the time.

Sorry for the confusion.

-David

As an aside, it's nice to finally see class libraries like these coming out that use attributes in Delphi to do truly useful things. I worked on a couple of parts of a big library that does this. I've seen a few articles on it, but hardly anybody uses attributes (in Delphi) for much more than simple tagging of things, like boolean flags or passing in parameters.

Here, they were able to use them to replace a huge amount of configuration data that needed to be created by hand in an XML file that then served as a knid of DDL to tell the rest of the run-time how to deal with stuff. Now the attributes allow the class constructors to use RTTI to extract the necessary metadata and generate the same descriptor tables used by each instance of the class (instead of relying on XML files, which can get out-of-sync with the actual class definitions).