Re: CORBA again
| From: | bob at thestuff dot net | Date: | Tue, 06 Jun 2000 17:01:31 +0000 |
| Subject: | Re: CORBA again | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-20353@lists.php.net to get a copy of this message | ||
Well, orbit-perl uses method 1) I think. using 2, until orbit gets a
finished interface repository, would require an interface repo from
another orb which will compicate things. 1 would work well enough, atleast
to start, and 2 can be implemented later on when orbits IR is finally
finished. Unless you have time to finish orbits IR now. :) Just my 2
cents.
On Tue, 6 Jun 2000, Tim Ritchey wrote:
> I started working on an implementation using ORBit, but the real-world got
> in the way, and I haven't made much progress since, but I will tell you what
> I know:
>
> A) The ORBit DII stuff had a bug or two that I submitted patches for, and
> now exist at least in the CVS version. DII is a must-have really.
>
> B) Of course, even with DII we need to have some way of correctly building
> the DII calls (i.e. we still need to know the proper types of each argument)
> and marshalling between the PHP variables and CORBA object operations. There
> are at least three ways of doing this
> 1. have the IDL available in some directory, parse it ourselves, and
> construct the Argument lists from this parsed IDL. This is the way the
> current loosely typed languages (i.e. Perl) integrate with ORBit.
> 2. Use an Interface Repository (IR) to grab the interface information
> dynamically. This is much more elegant, but unfortunately ORBit's IR is in
> an indeterminant state. This is not necessarily a big deal - ORBit is only
> providing the client-side ORB - we can assume that the Objects we are trying
> to access have registered with an IR - and this IR could be from another
> ORB.
> 3. Use some proprietary file format that describes the types of method
> arguments without all of the other IDL baggage, and parse this simplified
> file to get the method argument types.
> 4. just thought of another - we could use some structure in the PHP
> script itself to define the function variables more prescisely.
>
> C) Finding the object we want to use is also important, so integrating the
> naming service is important.
>
> Anyway, I got some rough code worked up, but got stalled at (B) trying to
> decide what to do. (2) is ideal, but we probably also want a fallback. I was
> designing it so that you could set an IDL repository directory in php.ini,
> and was going to pull the parsing code from the ORBit-Perl, and use that to
> save some work. If anyone is interested in helping, or seeing what I did,
> let me know. It is pretty rough, doesn't work at all, and might just be the
> ravings of a lunatic.
>
> I was planning on picking it up again this week and hacking on it. Does
> anyone have a preference for the different methods of grabbing the method
> argument types? I am planning on going with (2), with (1) as a fallback.
>
> Cheers,
> tim
>
> ----- Original Message -----
> From: <bob@thestuff.net>
> To: "David Eriksson" <david@2good.nu>
> Cc: <php-dev@lists.php.net>
> Sent: Tuesday, June 06, 2000 11:26 AM
> Subject: Re: [PHP-DEV] CORBA again
>
>
> > I havent seen anything about it. I'm very interested in CORBA support
> > though for my project BLADE (http://www.thestuff.net/bob/projects/blade)
> > since it uses CORBA extensively and would like to get PHP support. ORBit
> > already has bindings for several languages, so I would think binding ORBit
> > would be the easiest way to go for support.
> >
> > On Tue, 6 Jun 2000, David Eriksson wrote:
> >
> > > Several people have talked about PHP and CORBA on this mailing list.
> Now,
> > > where is the implementation? :-)
> > >
> > > I would very much like to see what progress has been made when it comes
> to
> > > using CORBA from PHP.
> > >
> > > I'll just start implementing it myself if nothing useful turns up...
> > >
> > > Regards,
> > >
> > > -\- David Eriksson -/-
> > >
> > > "An expert in a particular computer language is really an expert
> > > in the work-arounds necessary to use this language to perform
> > > useful work." - Richard B. Johnson
> > >
> > >
> > >
> > > --
> > > PHP Development Mailing List
> > > <http://www.php.net/>
> > > To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net
> > > For additional commands, e-mail: php-dev-help@lists.php.net
> > > To contact the list administrators, e-mail: php-list-admin@lists.php.net
> > >
> >
> >
> > --
> > PHP Development Mailing List <http://www.php.net/>
> > To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net
> > For additional commands, e-mail: php-dev-help@lists.php.net
> > To contact the list administrators, e-mail: php-list-admin@lists.php.net
> >
> >
>
>
> --
> PHP Development Mailing List <http://www.php.net/>
> To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net
> For additional commands, e-mail: php-dev-help@lists.php.net
> To contact the list administrators, e-mail: php-list-admin@lists.php.net
>